Re: Criticism of "version numbering"-document

From: Date: Mon, 08 Mar 2004 18:17:14 +0000
Subject: Re: Criticism of "version numbering"-document
References: 1  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-875@lists.php.net to get a copy of this message
On 8 Mar 2004 at 18:40, Pierre-Alain Joye wrote: > On Mon, 08 Mar 2004 15:51:07 +0100 > stefan@neufeind.net (Stefan Neufeind) wrote: > > > > Nice to hear that. So I'm not alone :-)) > > RC is not a state but it is part of the version number. RC state is > beta. > > > > > 2. we dont have a state "RC" (yet) > > > > Agreed. > > nope. Oops, now that you mention it ... okay, sorry for the over-sight! > > > 3. during earlier discussion (specifically while talking about the > > > BC breaking releases regulation) on this it was decided that new > > > major version continue the version counting where the previous > > > package left off .. which is why the first release of MDB2 was > > > 2.0.0alpha1, and the next 2.0.0beta1 with the final stable being > > > 2.0.0 > > > > Well I see what you mean. But is it realistic to assume that > > between alphaX, betaY and the stable no new features will be added > > or changed or anything? If that occured already a new sub-release > > (x.x.Y) would have been required. Maybe people like seeing a 2.0.0 > > being released as stable. But why would a 2.0.2, state stable have > > been a problem? The initial 2.0-kickoff would have been "new API, > > but currently in the works". imho no problem with that. And then > > 2.0.1 as beta and 2.0.2 as stable could have followed. > > As it is a whole new package, we may start from the beginning, ie > MDB2-0.1.0 . It is a common situation for many projects. Generally agreed. This would also solve the problem of having states <1.0.0 again (everything under 1.0.0 not stable). But when would a new major version be used in that case? Wouldn't we end up with packages all <2.0.0? Hmm - no good solution either. I don't have a clue how we could solve the numbering-problem (maybe others have?). But imho we should avoid the current state-postfix (and another revision-number after that). > > > The solution used in the version naming regulation takes a > > > straighforward way of making things work. > > > > > > There are other solutions: > > > 1) add the state whereever we currently only show the version name > > > > Would be fine with me, yeah. Or if, for obvious reasons, we don't > > want to do it that way then I'd suggest to at least make it > > "2.0.0alpha" instead of adding another versionnumber after that. > > > > Why not a version-numbering like that: > > > > 2.0.0alpha > > 2.0.1alpha > > 2.0.2beta > > 2.0.3 > > I do not like 2.0.0state. Redundant with the state flag itself. > Adding the state in the package archive name is not a problem. As far > as I remember, the state is displayed everywhere else (cmd line, pear > web,...). Agreed. The only consequence, as Lukas pointed out, that e.g. the first stable of 2.x could be 2.0.6 or so ... but that's fine with me, for the benefit of not over-complicating/poluting version info with states etc.). And "latest stable" etc. are in most cases >x.0.0 anyways :-)) Stefan

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