[Gtk-sharp-list] API Freeze Policy Adjustment

[Chris Ridd]

On 1/7/04 11:04 pm, Todd Berman <tberman@off.net> wrote:

> Murray Cumming wrote:
>> On Thu, 2004-07-01 at 17:06 -0400, Todd Berman wrote:
>> 
>>> Mike is saying that API that is bound and *WILL NOT WORK* can be fixed
>>> so that it will work. This wont break anything for anyone.
>> 
>> 
>> I have no objection to that, as I have made clear. But he is also saying
>> that he will make large API additions. That is not OK, as I have
>> explained. I encourage you to read the whole thread.
> 
> Where did Mike say he plans on large API additions? I must have missed
> that part of the thread.

I think it was on his blog, presumably this article:

<URL:http://primates.ximian.com/~mkestner/weblog/pivot/entry.php?id=44>

In particular, this paragraph:

----
The API freeze that we have in place now for 1.0 still allows us to fix
broken API bindings. We are also going take advantage of the nice Assembly
versioning and GAC functionality of mono to allow the addition of missing
API related to the 2.2 Platform and convenience overloads for methods. This
gives us a fair amount of flexibility to continue to improve the 2.2
bindings for a while, without breaking existing code developed against Gtk#
1.0. As an app developer, sticking with 2.2 should not disappoint you too
much, since using newer API locks your app out of the still enormous Gnome
2.2 installed base.
----

Cheers,

Chris