Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89557
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain hristov.com from 91.196.125.214 cause and error)
References: <DUB128-W930E1C18231D67D9FA0DE7BA060@phx.gbl>
 <045401d12cd3$d7d57ff0$87807fd0$@belski.net> <565EA53F.5050507@php.net>
 <047301d12cdd$5e248020$1a6d8060$@belski.net> <565FD845.7090502@php.net>
 <C7409B50-A31F-4427-8F4E-31D5ED9ABFFE@zend.com>
 <007001d12da4$5b044cf0$110ce6d0$@belski.net> <565FFF89.2050604@php.net>
 <012401d12db7$a43cd410$ecb67c30$@belski.net> <56602062.90905@php.net>
 <CAEZPtU5wyrkuAhgukvKGoZMR0U=eZS-Nq0jC3PjfrnWFcZNwzg@mail.gmail.com>
 <56602433.8090608@php.net>
 <CAEZPtU4DeCQAZw3pFoYJmtkovVQ7ofM4y5AqCxVEqZPuhcPgcg@mail.gmail.com>
 <56602CB9.3000007@php.net>
To: PHP internals <internals@lists.php.net>
Message-ID: <5660339B.6000805@hristov.com>
Date: Thu, 3 Dec 2015 13:20:43 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <56602CB9.3000007@php.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] PHP 7.0.0 final RTM delay
From: php@hristov.com (Andrey Hristov)

  Hi,
guys, just go out and say to the public, that due to Openssl security 
fixes which are awaited and thus because we want to ensure that 7.0.0. 
will be correctly working with it, we won't release 7.0.0 even as source 
until we are sure the QA procedure is gone.

PHP can get really good bashing for being too hasty out of the door not 
working with latest and secure OpenSSL.

You know me, I am far from a Windows fan, it makes just send. The 
Openssl update is force majeure.

Best,
Andrey

On  3.12.2015 12:51, François Laupretre wrote:
> Le 03/12/2015 12:28, Pierre Joye a écrit :
>> On Thu, Dec 3, 2015 at 6:14 PM, Sebastian Bergmann <sebastian@php.net>
>> wrote:
>>> Am 03.12.2015 um 12:10 schrieb Pierre Joye:
>>>> In my world, we build softwares from sources, then we may found
>>>> issues. We patch the sources to fix them and make everything work
>>>> together smoothly.
>>>   Are you suggesting that PHP 7.0.0 will be changed, re-tagged, and then
>>>   released without a new release candidate if you find a problem
>>> building
>>>   it for Windows?
>> Can you at least give me the illusion that you read our answers? It is
>> not only about windows.
>>
>> I think it is confusing enough without trying to add more
>> "suggestions" to the stack.
>>
>> What I am saying is simple. Openssl will release security related
>> fixes today. Most if not all of them will hit 3rd party
>> packagers/distros today/tomorrow/soon. Now, after discussions, waiting
>> a couple of hours more sounds like a sane (if not only) move to ensure
>> that everything goes well with openssl and php 7. If that's not the
>> case, for example openssl breaks BC again, then it is a problem in
>> openssl and they should delay their release or distros/3rd parties
>> will delay the patches. It won't have an impact on today planed
>> release of php 7.
>>
> For subsequent important releases, could we introduce a concept of
> 'frozen zone' of one or two days before the planned release date. This
> is a time where everything is ready to deliver and nothing is planned.
> Any event during this time delays the date. That's one of the mechanisms
> NASA has established to respect launch times and I find it quite efficient.
>
>