|
From: John D. <jo...@de...> - 2009-11-17 17:55:46
|
David Brownell <da...@pa...> writes: > On Tuesday 17 November 2009, Øyvind Harboe wrote: >> >> > What would you think makes a release deserve to be called "1.0"? >> >> >> >> Basically, we need to run out of our list of "things to fix". >> > >> > So there will never be a 1.0 release, then... >> >> Lots of respectable projects never make it to 1.0. > > My point being to emphasize that if that's the model, then there > is no point in having a "major" digit in the release number. It > might as well be dropped, since it's permanently meaningless. How about using the major version number (after 0) to indicate *stability* from the point of view of user. As in, all commands that work in 1.1 will continue to work until 2.0. If we want to remove deprecated commands, or change the syntax in an incompatible way, these changes should be held until the next major version. -- John Devereux |