[Gtk-sharp-list] API Freeze Policy Adjustment

Murray Cumming murrayc@murrayc.com
Fri, 02 Jul 2004 10:33:27 +0200

On Thu, 2004-07-01 at 18:04 -0400, Todd Berman 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.

His blog entry suggests a lot more than that, and that's why I'm
mentioning it:
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."

It is a waste of time to argue so energetically if you have not read the
thread so you don't even know what is being dicussed.
> >>Do we need to get someone on the release team so we can ok our breaks 
> >>like you do?
> > 
> > 
> > No, just follow the regular, well-known, documented freeze-break
> > approval process:
> > http://developer.gnome.org/dotplan/tasks.html#ApprovingFreezeBreaks
> > 
> Which you just said yourself you don't follow. How can you expect other 
> binding writers to follow a specification that you are incapable or 
> unwilling to follow?

I challenge you to find any large API change in a gtkmm stable series.
Murray Cumming