Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74956
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.169 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <53A07DCA.9010702@sugarcrm.com>
References: <53886F73.70402@php.net> <CANzZr6k7=+eV69y7OSQuM5ThhNOEmrKLj-RUQy2o4qDdW=sTHQ@mail.gmail.com>
 <538EAD75.5020402@fedoraproject.org> <CAEPJdumPPUM6bkVa1ACXkREsOCpPGrOjGJeRKgAhho-H+JkE4g@mail.gmail.com>
 <CAMUwpuTZxoOgKHbJ5xMBfj-yYFQW3QAaBSVq+UYDrGkTX=YWYg@mail.gmail.com>
 <CAEPJdukpDboN-d=8TSpQZ6FHXeatj=RLhzAmRhNwWA8B+Ucx1A@mail.gmail.com>
 <CAEPJdukpcq6MikdkOfB=Qrw37M15NGK7MFPUTLjrLoHu5g=rfA@mail.gmail.com>
 <CAMUwpuReCN-QaN=wHLcgAb=Z0sLXNtHqkcGS63_bOboBNd37ew@mail.gmail.com>
 <CADyq6sJWVWH+74tppTX3Fun6YwZD=L=hMOOH5OGDUcXjKjrCiA@mail.gmail.com>
 <CAMUwpuRTd2i24Y8V+ONqnjyhZB3cfQG+C+9h1TFpWmoKVqdyLQ@mail.gmail.com>
 <CAH-PCH5TvCtL21J-GyUaJ99OQm+AZ9sd1dkj0i4=5FPUdTirBA@mail.gmail.com>
 <CADyq6sKFmpvTn5RwP1N1kcqZ2WCsp4TEmaNygi29JV76N7S6_w@mail.gmail.com>
 <539B0888.9040208@fedoraproject.org> <CADyq6sLTKNa6V-R0Y97fEzGLMLCaAys3S9Hu0Sijzb2isMnrFg@mail.gmail.com>
 <CAOhuFvYuVhe1BDYQSfnftaTMNVeOZnXL482Sx3r508jhSyVsfg@mail.gmail.com> <53A07DCA.9010702@sugarcrm.com>
Date: Tue, 17 Jun 2014 20:40:58 +0200
Message-ID: <CAMUwpuTqj6hsowHcvc_3RYytk8iAp_w9NNB=zm9boKsxrxR93w@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Rafael Dohms <listas@rafaeldohms.com.br>, Marco Pivetta <ocramius@gmail.com>, 
	Remi Collet <remi@fedoraproject.org>, internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] BC break in 5.4.29 and 5.5.13
From: jpauli@php.net (Julien Pauli)

On Tue, Jun 17, 2014 at 7:41 PM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>> It has been 18 days without a 5.5.14 release or a rollback of 5.5.13.
>> This is highly unacceptable and irresponsible of a core language.
>
> We have a release schedule. Which is widely known - in fact, we've just
> announced 5.5.14 RC1 last Thursday. I agree BC break is bad but not bad
> enough to break the release schedule. If you suffer from this particular
> problem, just keep on 5.5.12 for 2 weeks. And please test the RCs, if
> people would actually test the RCs we'd know about such problems
> *before* the release, not *after*. That's what RCs are for.

And here Stas you get my huge +1.
I cant understand the stress about this bug. It seems like the earth
is gonna blow up.
Suddenly, people are not "stuck with" 5.3.x anymore (thing we still
ear about, nearly daily), but they do run exactly 5.5.13. Common, are you
kidding ?

Just stay in 5.5.12, keep calm as there really is no need to lose
anyone's temper.
It is a BC break, yes, and we all apologize about it, believe it. But
it won't blow the earth up in the few next seconds, will it ?

The only moments I know we've been releasing a new version in rush,
was about huge security holes that got disclosed just after a release.

However, as I can see the patch seems to still have problems in our
RC1, we could go for an RC2 if no consensus is found about it before
next tuesday (the day we usually tag).
What do you think about this ?
Like Ferenc said, rushing a patch is a high risk at introducing
another bug, or just not fixing the bug properly. And then a bad
loop's gonna start from that.
Let's take time to test our patches / solutions, to keep our level of
quality. If RC2 is needed, there will be an RC2 (and more again if
needed). I'am all in favor of improving our quality , which usually is
the opposite of rushing.

Julien Pauli