Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42975
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.116 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 7 Feb 2009 21:54:05 -0800
Message-ID: <698DE66518E7CA45812BD18E807866CE028675DC@us-ex1.zend.net>
In-Reply-To: <1F10838B-A3AB-422E-9AB1-6AAECC370990@pooteeweet.org>
Thread-Topic: [PHP-DEV] towards the next 5.3 release
Thread-Index: AcmI+dLUzBo88Vs3Qn2VPeOlFc+2twAt1vCg
References: <5EC76153-898F-49C2-BDF1-C227578DB874@pooteeweet.org> <698DE66518E7CA45812BD18E807866CE02867546@us-ex1.zend.net> <1F10838B-A3AB-422E-9AB1-6AAECC370990@pooteeweet.org>
To: "Lukas Kahwe Smith" <mls@pooteeweet.org>
Cc: "php-dev List" <internals@lists.php.net>
Subject: RE: [PHP-DEV] towards the next 5.3 release
From: andi@zend.com ("Andi Gutmans")

> -----Original Message-----
> From: Lukas Kahwe Smith [mailto:mls@pooteeweet.org]
> Sent: Friday, February 06, 2009 11:57 PM
> To: Andi Gutmans
> Cc: php-dev List
> Subject: Re: [PHP-DEV] towards the next 5.3 release
>=20
> Well we have established the primary testers mailinglist for this
> purpose. However the current release plan only includes mailing this
> list when the RC stage has been reached:
> http://www.php.net/reST/php-src/README.RELEASE_PROCESS
>=20
> So obviously this list can be used to get in contact with this group
> of projects. Maybe it makes sense to include them in x.y.0 releases.
> Then again the plan was to mail them once we hit RC1 anyways ...

OK that's good although it may make sense to push that up to beta.
In the past we have looked at Release Candidates as ("We think it's
ready to release and if no one finds critical bugs we could just rename
the package"). I doubt this is where you think we're at now and it's
more about making sure we get broader testing. It's a bit of a chicken
and egg so I understand the benefits of calling it RC. I guess what I
was suggesting was that we at least have folks do a quick sanity with
applications so we feel good about going into the RC.

Andi