Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63716
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 217.114.211.66 as permitted sender)
Message-ID: <508F971F.2000009@php.net>
Date: Tue, 30 Oct 2012 10:00:15 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121016 Thunderbird/16.0.1
MIME-Version: 1.0
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Branching PHP-5.5
From: dsp@php.net ("dsp@php.net")

Hi Internals,

it's been a while since we started talking about PHP 5.5 and we are
already a little bit late with my release plans. I've started reviewing
the current master and came to the conclusion that it does make more
sense to me to branch 5.5 of master for a few reasons:

 (1) Parts of master are still from SVN times making it very hard
     to figure out if they are already merged to 5.4 or not as they
     have different version numbers.
 (2) The release process aimed to make new features and changed
     available faster, so I want to make sure everything is included.
 (3) There would be 2500 unique commits to be reviewed that are
     different from 5.4 (because of the SVN import).

Also we have barely BC breaks in master and nothing that cannot be
fixed. In particular:

 9e7ae3b Allow management of your own padding in openssl_encrypt/decrypt
 This changed a parameter from bool to long, but the value 1
 is equivalent to passing bool to the former signature, therefore
 it is BC.

 f28c128 Return previous error handler when resetting the error handler
 This might lead to problems in case people are testing === to
 test the return value of set_error_handler()

The rest looks fine to me. So I'll go ahead and start PHP-5.5 branch by
Thursday from current master. I know we then have 4 active branches
which is a pain to keep in sync and merge and I am open for suggestions.

A first alpha is planned for Nov 22. We still accept new features, so no
worries.

Please note we are about 1 1/2 month late to the 5.4 release last year,
so expect a final of 5.5 around April 2013.

Please make sure that your changed to 5.5. that are not in 5.4 are in
the NEWS entry. There are still a lot of changes missing in NEWS.
Also we have 37 expected test failures and 2 test failures (on my machine).

Regards
 David Soria Parra