[Mono-dev] Planning: Mono version numbers.
marek.safar at seznam.cz
Fri May 11 19:16:15 EDT 2007
> We have basically mixed .NET API-matching features, with our
> own API features, and with runtime changes. In addition, the 3.x
> work really will come out completely out of sync: 3.5 is a lot simpler
> and easier to reach than 3.0 is.
Just to confuse everyone even more 3.5 will contain Greed Bits and
Red Bits. It means that 3.5 will overwrite 2.0 core libraries like
I did quick diff between 3.5 B1 mscorlib and 2.0 RTM mscorlib and
what I found is
25 new methods/properties
1 removed method/property
3 warnings (changed attributes, base classes, etc.)
> Maybe we need something like this:
> * Mono A: Estimated 3-4 months of work.
> The core 2.0 done + ASP.NET 2.
> 2.0 profile (minus Winforms) becomes officially supported.
> * Mono B: Estimated 6-9 months of work.
> When Windows.Forms 2.0 is complete
> * Mono C: 9+ months.
> When the Compacting GC is done
> Make the runtime embedding API changes here.
Hopefully will make it into Mono 2.0
> * Mono D: 9+ months.
> When the new IR/optimization framework is ready
> * Mono E: 6-9 months of work.
> When System.Core and other 3.5 libraries are finished
> maybe we could even split this up in chunks.
I am just not sure whether we should include .NET 3.0 into our releases
or keep it separate, e.g. Mono Fx 1.0 Release
More information about the Mono-devel-list