[Mono-dev] [Fwd: Planning for Mono 1.2: API freeze.]

Kamil Skalski kamil.skalski at gmail.com
Mon Jan 2 13:07:27 EST 2006

There is still a pending patch for

I'm not sure if this could be called a "mono specific public API", but
in some way a script name is such an API ;-)

2006/1/2, Miguel de Icaza <miguel at novell.com>:
> --
> Miguel de Icaza <miguel at novell.com>
> Novell, Inc.
> ---------- Wiadomość oryginalna ----------
> From: Miguel de Icaza <miguel at novell.com>
> To: Mono Hackers <mono-hackers-list at lists.ximian.com>
> Date: Mon, 02 Jan 2006 12:54:19 -0500
> Subject: Planning for Mono 1.2: API freeze.
> Hello folks,
>     I know that this is a very short notice, I should have mentioned
> this in mid-December, but I completely blanked out.
>     We are going to API freeze Mono this week.  If you have any API
> changes that you want to make, please contact me directly.
>     What this means is that the public API of the Mono-specific
> libraries will cease to change, although we can continue to bug fix it
> and document it.
>     The .NET libraries already had their APIs set in stone, so those
> will continue to be developed (implementing NotImplementedExceptions,
> fixing bugs and implementing NET_2_0 protected code).
>     Changes to the .NET public API to fix differences against the
> published .NET interface is ok (specially in the 2.x universe, as Mono
> 1.2 will not guarantee .NET 2.0 support in full anyways, so things are
> much more lax there).
>     So in short: you can change implementation bits, but not public
> interfaces.
>     If an API change is /absolutely required/ this needs to be discussed
> before the patch makes it into SVN.
> Miguel
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

Kamil Skalski

More information about the Mono-devel-list mailing list