Re: Criticism of "version numbering"-document
| From: | Lukas Smith | Date: | Mon, 08 Mar 2004 17:37:54 +0000 |
| Subject: | Re: Criticism of "version numbering"-document | ||
| References: | 1 2 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-871@lists.php.net to get a copy of this message | ||
Stefan Neufeind wrote:
Right between beta and stable you mean? That's also fine with me, yeah. Then we should have a hierarchy of cvs -> alpha -> beta -> rc -> stables/cvs/devel
3) dont continue counting on new major versions, soExactly. It is confusing as MDB2 1.0.0 might get confused with MDB 1.0.0 and vice versa. At the same time I find it "ugly" if the first stable release of a major version is not "x.0.0", because then it becomes very untransparent to all outsiders that a given package is no finalizing its API. This is why we ended up with the current proposal Note there was also opposition about the must have an RC before making the first stable release. This was also a step in ensuring that people know when an API is being finalized. Who knows that 2.1.6 stable is the first stable release of major version 2? Not unless you take a look at all previous releases and/or the changelog. Just as much nobody knows that 2.1.5 RC is the release candidate just before that first stable release. 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 07my first MDB2 release could have been 0.1.0 with state alphaWell, I think this is no option since it has already been discussed quite long. At that time some people pointed out that end-users (not devs) might be confused with a "MDB2 1.0" and "MDB 2.0" or something. A clean solution would have been to use "MDB 2.x"-naming, but since PHP does not support namespaces we at least need to rename the class MDB to MDB2 (and the sub-directory also) in that step. So we agreed that maybe having a MDB2 (or MDBv2 or MDB_v2, in that order, as appropriate) would be the best solution. Again, I'm not saying that the group has made a bad, not well-thought about decision. And it *might* make sense to demand to append the state to the name since not in all places the state-field might be yet implemented (visible). But imho there are only two "good" options: a) Going for a "2.0.1alpha"-name instead of "2.0.0alpha2". b) Implement the missing indicators for the state where possible and avoid having the state in the package version completely. (imho *really* the best and cleanest solution).