Re: README.RELEASE_PROCESS: misleading branching info?

On 05.06.2018 at 18:22, Sara Golemon wrote: > On Tue, Jun 5, 2018 at 6:37 AM, Christoph M. Becker <cmbecker69@gmx.de> wrote: > >> README.RELEASE_PROCESS[1] states in the “Rolling a non stable release >> (alpha/beta/RC)” section[2]: >> >> | 4. Checkout the release branch for this release (e.g., PHP-5.4.2) from >> | the main branch. > > "the main branch" is quite misleading, I agree. > It should perhaps be something like: > > 4a. If this is an alpha release, checkout the master branch. > 4b. If this is a beta release, checkout the previously forked > development branch (e.g. PHP-7.3) > 4c. For RC releases, checkout a release branch (e.g. PHP-7.2.0) cut > from the appropriate maintenance branch (e.g. PHP-7.2) if required. Thanks, that sounds plausible. Some of the following items would need adjustment as well, for instance, “8. If all is right, commit the changes to the release branch with `git commit -a`.” If nobody beats me to it, I shall improve README.RELEASE_PROCESS in this regard during the next few releases. -- Christoph M. Becker