Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20637 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46174 invoked by uid 1010); 27 Nov 2005 05:23:58 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 46158 invoked from network); 27 Nov 2005 05:23:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Nov 2005 05:23:58 -0000 X-Host-Fingerprint: 70.85.46.36 unknown Received: from ([70.85.46.36:52431] helo=prohost.org) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 57/73-56276-DE249834 for ; Sun, 27 Nov 2005 00:23:57 -0500 Received: (qmail 19332 invoked from network); 27 Nov 2005 05:23:53 -0000 Received: from prohost.org (HELO ?127.0.0.1?) (70.85.46.36) by prohost.org with SMTP; 27 Nov 2005 05:23:53 -0000 Message-ID: <438942E8.7090006@prohost.org> Date: Sun, 27 Nov 2005 00:23:52 -0500 User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthias Pigulla CC: Sebastian Bergmann , internals@lists.php.net References: <00A2E2156BEE8446A81C8881AE117F192C1D29@companyweb> In-Reply-To: <00A2E2156BEE8446A81C8881AE117F192C1D29@companyweb> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: AW: [PHP-DEV] Re: PHP 5.1 (Or How to break tousands of apps out there) From: ilia@prohost.org (Ilia Alshanetsky) Matthias Pigulla wrote: > I have to back Sebastian with what he said. Obviously the release methodology currently applied does NOT work, neither for the project nor the community around it. It has worked for many years, just because of one problem you don't scrap the process. > BUT: Once you agree the work is done on a branch and you make something available that has a RC in it's version name, it's GAME OVER. No more features. Only bugfixes. RCs are there for testing, if you don't test them don't complain when things break. The main reason for RCs is to spot critical bugs and important regressions. Some of those are test suit can pickup, but most issues are discovered through "real" usage. > You cannot expect folks to re-test everything with every new RC, and so it's not PEAR's fault if they were not the first to notice the problems. That is exactly what's expected. > Remember the discussion about curlies? I also never understood why that had to be tackled in an RC5. They were removed. Ilia