Re: Criticism of "version numbering"-document
| From: | Cipriano Groenendal | Date: | Mon, 08 Mar 2004 20:28:22 +0000 |
| Subject: | Re: Criticism of "version numbering"-document | ||
| References: | 1 2 3 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-884@lists.php.net to get a copy of this message | ||
> Yeah I agree that its ugly to loose out all the nice version numbers
> since we start at x.0.0 for major versions greater than 1.
>
> So maybe the solution is to start new major version out with a version
> number below 1.0.0 and then have them move to x.0.0 on the first RC or
> stable release, where x denotes the major version number.
>
> So in that case my first alpha release for MDB2 could have been 0.1.0
> and the next beta would be 0.2.0 (since I added features) and then
> 2.0.0RC1 and then finally for the first stable release 2.0.0. With the
> state not being appended and RC not being a state and using state beta
> instead.
This seems to be a nice compromise. Most people already tend to see 0.x.x as
non-stable versions, but if you jump from 0.x.x to 2.0.0 you clearly
instantly mark the package as
stable, and MDB2 2.0.0 > MDB 1.15.99. The
only time where a confusion could arrise is when comparing between say MDB2
0.1.0 and MDB 1.2.3. But most of the people willing to go for an unstable
package, will hopefully be able to figure out the difference between these
two, and end-users that may have more difficulty in interpreting version
numbers, will usually stay away from any 0.x series, and pick MDB-1.2.3.
I'd say a big +1 for the 0.9.9 -> 2.0.0 jump Lukas posted.
Cipri