[Mono-dev] [Ximian-mono-list] Planning: Mono version numbers.

Massimiliano Mantione massi at ximian.com
Fri May 11 15:46:07 EDT 2007

On Fri, 2007-05-11 at 14:13 -0400, Miguel de Icaza wrote:
> [...]
>     So what we need is to come up with a new release number scheme for
> the above.   

Just my 2c, and it might look really gross...

Calling versions "major.minor", I'd do the following:
- Increment "major" at release "C" (compacting GC and API changes),
  especially because of the API changes.
- Increment "minor" for every other release, number assigned with
  a "first come, first served" policy between the releases :-)
Trying to assign numbers now, before we know what will be ready
first, is inappropriate IMHO.

Since it's *likely* that A and B will become ready before the rest,
this *could* mean:
- "1.4" => Mono A
- "1.5" => Mono B
- "2.0" => Mono C
- "2.1" => Mono "whatever comes next"...
But if the order in which things get ready changes, this scheme
changes accordingly.

And people should read the release notes to see what's shipped,
what's supported and what's not.

I said it was gross :-)
But at least it's easy...

Otherwise, we should use-choose numbers for "marketing" reasons,
but this is beyond my capabilities ;-)


More information about the Mono-devel-list mailing list