Repository navigation
Conversation
c55dff1 to
5c5121e
Compare
5c5121e to
373a7b6
Compare
Push the tag and tarballs only to php-src-staging and web-php-distributions-staging on packaging day and publish them on the announcement day. This avoids exposing security fixes before they are announced. Also fix the broken step numbering in the stable release announcement section. [ci skip]
373a7b6 to
6f2281a
Compare
Understandable for releases with security fixes, but the documentation makes it seem like we should always use -staging even when there are no security fixes - why? |
| git checkout -b php-X.Y.Z-local-release-branch upstream/PHP-X.Y.Z | ||
| git checkout -b php-X.Y.Z-local-release-branch PHP-X.Y.Z |
There was a problem hiding this comment.
Should this branch be created from PHP-X.Y.Z in php-src-staging or from the primary php/php-src repo?
There was a problem hiding this comment.
It's the staging at this stage but it's also present locally so it doesn't need to specify remote https://github.com/php/php-src/pull/24415/changes#diff-0dcedaa4ee53dc5c04ab85c58b9527b34c8ee97b6a86f1efd8e15a7237fa5fb7R578
Push the tag and tarballs only to php-src-staging and web-php-distributions-staging on packaging day and publish them on the announcement day. This avoids exposing security fixes before they are announced.
Also fix the broken step numbering in the stable release announcement section.