Re: Re: Making a release

From: Date: Fri, 05 Mar 2004 14:22:32 +0000
Subject: Re: Re: Making a release
References: 1 2  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-839@lists.php.net to get a copy of this message
Stefan Neufeind wrote:
On 5 Mar 2004 at 14:53, Lukas Smith wrote:
Stephan Schmidt wrote:
Hi,
Why not simply release an alpha as a first release? No BC problems and allow QA to really test it as a normal package. And not only QA can play with it.
I'll release it as 0.6 beta. There probably won't be any major API changes and BC is no problem in version below 1.0
Just as an FYI: the version number needs to include the patch level as well. So you guys should actually be talking about: 0.6.0 and 1.0.0 etc.
And also a "alpha1"-addition which would make it 0.6.0alpha1 ?? I'm just reading that again from http://pear.php.net/group/docs/20040226-vn.php and I must say I'm a bit surprised why this complicated way was chosen. Why e.g. alpha2? Why not 0.6.1alpha?
The reason why the state was added to the version name is as follows: - it is php standard to do this for RC state (also there is no state RC in the package.dtd) - once you update to a new major version you start off with 2.0.0alpha1 for example, then you continue with 2.0.0alpha2, possibly followed by 2.0.0beta1 and then 2.0.0RC1, 2.0.0RC2 and then 2.0.0
PS: This is not "critism against a group-discussion". Maybe I simply got things wrong ...
you can critize the group .. we are humans and can make mistakes :-) regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07

« previous php.pear.qa (#839) next »