Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:88740 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84207 invoked from network); 10 Oct 2015 18:56:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Oct 2015 18:56:18 -0000 X-Host-Fingerprint: 176.248.2.89 unknown Received: from [176.248.2.89] ([176.248.2.89:17494] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E9/E4-44453-15F59165 for ; Sat, 10 Oct 2015 14:56:17 -0400 Message-ID: To: internals@lists.php.net References: Date: Sat, 10 Oct 2015 19:56:14 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:41.0) Gecko/20100101 Firefox/41.0 SeaMonkey/2.38 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 176.248.2.89 Subject: Re: removal of the old PHP-X.Y.Z release branches From: ajf@ajf.me (Andrea Faulds) Hey Ferenc, Ferenc Kovacs wrote: > Hi, > > we RMs started using the release branches (PHP-X.Y.Z) a while ago and we > push those so that the we can work together easier when preparing/syncing > the releases. > As those branches are meaningless for the general public I would propose > updating our current release process ( > https://github.com/php/php-src/blob/master/README.RELEASE_PROCESS) so that > when we create a new release branch (PHP-X.Y.Z) we also remove the old > release branch (PHP-X.Y.Z-1). Once a release is made it is tagged, so the branch is then entirely redundant, right? Or are branches sometimes ahead of the tag? Assuming the former, then getting rid of the branches once the release its tagged makes perfect sense to me. Much less needless git clutter. Thanks. -- Andrea Faulds http://ajf.me/