[Omake] Releases and versioning (0.9.8.2, 0.9.8.3, 0.9.9, 0.90.0, ...?)

Aleksey Nogin nogin at metaprl.org
Wed May 30 11:29:44 PDT 2007


On 30.05.2007 10:36, Jason Hickey wrote:

> Here is a numbering proposal.
> 
> There are two major pending works.
> 
>    - keyword arguments
>    - naming.
> 
> Suppose we abandon the strictly <1 numbering convention, allowing 
> release numbers 1+.  We could do this:
> 
>    0.9.8.2 -> 0.9.9
>    0.9.8.x + keyword -> 1.0.0.rc1
>    0.9.8.x + keyword + naming (var3), auto, const, dll, etc -> 1.1.0

My main issue with this approach is that calling a release "1.0" implies 
an obligation to make sure it's "extra stable". I think that it might be 
a waste of time to work on such "extra stability" until after the 
"naming" code is fully incorporated. I would prefer to stabilize the 
"code refactoring" and "keyword" stuff only as much as needed to created 
a solid base for the "naming" merge and concentrate the real 
stabilization efforts on post-"naming" code. This is the reasoning 
behind aiming to have the "post-naming" become the 1.0...

> With the 0.9.9 announcement, we would advertise the 1+ versions also.
> 
>    0.9.9.x: bugfixes only (stable)
>    1.0.0.x: bugfixes only
>    1.1.0.x: development; when stable, released as either 1.2.0 or 2.0.0
> 
> It is important to me that these be announced, so that we can get 
> feedback _and_ let the community know what is in store.  I can do a 
> writeup on the 1+ stuff.

I agree. Once we decide on the numbering scheme, we should write some 
sort of a "Roadmap.txt" document and include it's contents in the future 
release announcements.

Aleksey


More information about the OMake-Devel mailing list