Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53628
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <slrnj0k74v.hbd.dsp@experimentalworks.net>
References: <4DFF7898.7010709@sugarcrm.com>
	<alpine.DEB.2.02.1106281143110.3774@whisky>
	<4E0A03AE.40907@sugarcrm.com>
	<alpine.DEB.2.02.1106281752450.3774@whisky>
	<4E0A07FC.4010808@sugarcrm.com>
	<CE41537C-76A9-4615-B0F3-9BB5C3C93D20@roshambo.org>
	<4E0A181C.7090105@sugarcrm.com>
	<slrnj0k74v.hbd.dsp@experimentalworks.net>
Date: Tue, 28 Jun 2011 20:35:13 +0200
Message-ID: <BANLkTimKMCxUrh5y1BG2Tqemv0sP38Ewpg@mail.gmail.com>
To: David Soria Parra <dsp@php.net>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] 5.4 alpha
From: tyra3l@gmail.com (Ferenc Kovacs)

On Tue, Jun 28, 2011 at 8:25 PM, David Soria Parra <dsp@php.net> wrote:
> On 2011-06-28, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
>> Hi!
>>
>> On 6/28/11 10:43 AM, Pierre Joye wrote:
>>> I do think we should repackage. There are many issues fixed since last
>>> week and it makes no sense to release something not representing what
>>> the current 5.4 branch is.
>>
>> Really, guys, if we ever want to have scheduled and orderly releases,
>> changing release schedule in the last minute repeatedly and repackaging
>> in the last second is exactly NOT the way to do it.
>>
>
> I agree with Stas. Repackaging in the last second might cause troubles
> and include obvious bugs. I prefer having a some time between packaging
> and releasing, if it's an alpha or not it doesn't matter. So in this
> case, to really try to finally stay on schedule , so we should release the
> already pacakged version and have an alpha2 in two weeks.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

wasn't the alpha1 packaged in the last second?
it was packaged on Jun 19, and it was planned to be released on Jun 20.
and it did include obvious bugs.
so if we already screwed up, we could at least fix what we can instead
of releasing a version, which we all know is broken.
this can make a bad impression in the early adopters.
but I won't whine much about this, just told my 2 cents.

Tyrael