Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102172
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 74.125.82.54 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <e2831e81-4829-b1ba-51eb-87de47793432@gmx.de>
References: <e2831e81-4829-b1ba-51eb-87de47793432@gmx.de>
Date: Tue, 5 Jun 2018 12:22:12 -0400
Message-ID: <CAESVnVoC9Y=gWMDQLxiwS9v3-TtB41z+SALSTQ9e+hbVAXH4vg@mail.gmail.com>
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] README.RELEASE_PROCESS: misleading branching info?
From: pollita@php.net (Sara Golemon)

On Tue, Jun 5, 2018 at 6:37 AM, Christoph M. Becker <cmbecker69@gmx.de> wro=
te:
> Hi!
>
> README.RELEASE_PROCESS[1] states in the =E2=80=9CRolling a non stable rel=
ease
> (alpha/beta/RC)=E2=80=9D 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.

> However, it seems that the PHP-x.y.z release branch is usually only cut
> shortly before GA[3].  Furthermore, the =E2=80=9CForking a new release br=
anch=E2=80=9D
> section states that the PHP-x.y branch is supposed to be cut shortly
> before the first beta release[4].
>
Indeed it is. The timetable I wrote up prior to the RM selection also
notes this: https://wiki.php.net/todo/php73

-Sara