Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20605
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 27 Nov 2005 00:24:25 +0100
Message-ID: <00A2E2156BEE8446A81C8881AE117F192C1D29@companyweb>
Thread-Topic: [PHP-DEV] Re: PHP 5.1 (Or How to break tousands of apps out there)
Thread-Index: AcXyoQUvDNU4EhCHQayHOn18rJofGQAPWQSw
To: "Ilia Alshanetsky" <ilia@prohost.org>,
	"Sebastian Bergmann" <sb@sebastian-bergmann.de>
Cc: <internals@lists.php.net>
Subject: AW: [PHP-DEV] Re: PHP 5.1 (Or How to break tousands of apps out there)
From: mp@webfactory.de ("Matthias Pigulla")

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.

Do it how ever you like - discuss whether it's legal to add new features =
on HEAD only or on release branches like Jani said.

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.=20

That is the only way for ppl to make sure there will be no unnecessary =
and unexpected changes anymore. Once my software passes tests with an =
RC, I can assume in good faith that it's very unlikely to break again.

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.

Remember the discussion about curlies? I also never understood why that =
had to be tackled in an RC5.

Should you find out late in this process a feature has been forgotten =
(i.e. #ifdef'd out) and you all agree that it has to go in - abort the =
RC phase, put it in again, restart (maybe with another RC name) to make =
ppl clear that they *do* need to re-test.

If you're kind, assert that there will be a certain time between RCs and =
releases, or communicate with your major community projects out there to =
make sure they do their work or do whatever.

But there is just a single simple basic rule that needs to be adhered to =
- that's all Sebastian pointed out.

-mp.


> -----Urspr=FCngliche Nachricht-----
> Von: Ilia Alshanetsky [mailto:ilia@prohost.org]=20
> Gesendet: Samstag, 26. November 2005 16:49
> An: Sebastian Bergmann
> Cc: internals@lists.php.net
> Betreff: Re: [PHP-DEV] Re: PHP 5.1 (Or How to break tousands=20
> of apps out there)
>=20
>=20
> No one project follows the same release methodoly, everyone=20
> uses what works for them and the community around the project.
>=20
> Ilia
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20
>=20