Re: Criticism of "version numbering"-document
| From: | Tobias Schlitt | Date: | Mon, 08 Mar 2004 19:05:04 +0000 |
| Subject: | Re: Criticism of "version numbering"-document | ||
| References: | 1 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-876@lists.php.net to get a copy of this message | ||
Hi all!
To get some more ideas inside I would like to add my 2 cents to that topic here.
Currently I'm using the pl<X>-suffix for my bugfixes in Image_Text, which is not really a clean way to handle this things. I will switch to usual version naming (x.y.z) in the next release. Just to clearify.
I agree with Stefan, that adding state information to the version number is pretty unclean in any way. A _version number_ should be a number. So, I'm pretty fine with adding a new state RC.
But, what in my opinion is still pretty mistakable, is the handling of versions greater than 2.0. IIRC we currently user 2.0.0alpha1, 2.0.0beta1, ... for version numbering what is specifically against the numbering below 1.0.0. A very common way in OS projects is to devide package states by the major version number, what we currently do for releases around 1.0, too. Everything below 1.0 is unstable, above is stable. The same is possible for versions greater than 1.0, if we handle even major versions as unstable (assumed that 0 is a even number) and odd versions as stable.
I guess this idea will bring up some more flames for me. ;)
Regards,
Toby
--
Tobias Schlitt
a passion for php http://www.schlitt.info