Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102162
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.21 as permitted sender)
To: PHP internals <internals@lists.php.net>
Message-ID: <e2831e81-4829-b1ba-51eb-87de47793432@gmx.de>
Date: Tue, 5 Jun 2018 12:37:35 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 8bit
Subject: README.RELEASE_PROCESS: misleading branching info?
From: cmbecker69@gmx.de ("Christoph M. Becker")

Hi!

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.

However, it seems that the PHP-x.y.z release branch is usually only cut
shortly before GA[3].  Furthermore, the “Forking a new release branch”
section states that the PHP-x.y branch is supposed to be cut shortly
before the first beta release[4].

So what is the proper procedure here?

[1] <https://github.com/php/php-src/blob/master/README.RELEASE_PROCESS>
[2] <https://github.com/php/php-src/blob/master/README.RELEASE_PROCESS#L66>
[3] <http://news.php.net/php.internals/101084>
[4]
<https://github.com/php/php-src/blob/master/README.RELEASE_PROCESS#L338-L341>

-- 
Christoph M. Becker