[Mono-dev] Mono version numbering
andreas.faerber at web.de
Wed Oct 31 14:09:18 EDT 2007
Am 30.10.2007 um 00:33 schrieb Jerry van Leeuwen:
> I think the only way to minimise confusion in the developer
> population that does not keep up-to-date with the details of
> development on Mono is to let at least the major version track
> full .NET compatibility. That is, do not move to v2.x.x until at
> least .NET 2.0 can be fully supported, do not move to v3.x.x until
> at least .NET 3.0 can be fully supported and maybe even do not move
> to v3.5.x until .NET 3.5 is supported.
> People that are aware of what is really going on under the hood
> will be able to make more detailed judgement calls and will not
> really care what version numbering you exactly use. It's the people
> that do not glance further than the version number that need to be
The problem with that Microsoft-ish numbering scheme and exactly
those people is that they might then start thinking they need Mono
2.x and Mono 1.x alongside just like Microsoft .NET Frameworks, and
start unnecessarily messing around with parallel Mono environments.
It's hard enough for those people to grasp that Mono ships multiple
C# compilers in a single version, unlike Microsoft.
So maybe we should move to another number system, Kanji or
More information about the Mono-devel-list