Re: glibmm not yet API frozen

[Vincent Untz <vuntz gnome org>]

Hi Murray,

Le mardi 18 mars 2008, à 07:08 +0100, Murray Cumming a écrit :
> On Sun, 2008-01-13 at 20:08 +0100, Vincent Untz wrote:
> > Le dimanche 13 janvier 2008, à 13:24 +0100, Murray Cumming a écrit :
> > > glibmm is not yet API frozen. In particular, we are still finishing the
> > > bindings for the new gio API in glib. We are generally working hard to
> > > get this done soon so we can be confident enough of the API to be stable
> > > before GNOME 2.22 is released.
> > > 
> > > I assume that this is more or less OK. glib and GTK+ don't follow the
> > > GNOME schedule so we generally don't expect glbmm and gtkmm to do so
> > > always.
> > 
> > Thanks for letting us know! It's fine, yes: the freeze is "hard" only
> > for the platform.
> 
> Sorry for the late reply, but I wanted to point out that this is wrong.
> The Platform Bindings must follow the schedule too, including the
> freezes, as much as is possible given that glib/GTK+ don't follow it
> yet. You do need to enforce this.

Well, for the bindings, I think it makes quite some sense to not freeze
the API at the same time as the platform. Else, in the worst case, you
could have only a few minutes to update the API to some new platform API
committed just before the freeze.

In my mind, it's similar to what we're doing with the desktop libraries:
the freeze exists and should be followed, but if people announced that
they need a change and the change is reasonable, there's no need to
reject the change. (in the case of the platform, the change has to be
only for some API added during the unstable cycle, unless the bindings
are parallel-installable with previous versions, etc.)

Vincent

-- 
Les gens heureux ne sont pas pressés.