On Sat, Sep 03, 2016 at 02:09:04PM +0100, Emmanuele Bassi wrote:
> https://blog.gtk.org/2016/09/01/versioning-and-long-term-stability-promise-in-gtk/
In the above announcement, you've written:
More details about these plans, including specifics for library
developers and distribution packagers, will follow in subsequent
blog posts.
Those subsequent blog posts have not yet been posted. If you've written
that, it probably means that you wanted to explain more things.
For a higher-level library based on GTK+, a GTK+ API break can force an
API break in the higher-level library. So during the GTK+ 3.9x versions,
the higher-level library cannot really guarantee API stability.
Normally, each time there is an API break, the Libtool version must be
bumped (increment CURRENT, set REVISION to 0 and set AGE to 0). Is that
all there is to know about handling API instability in higher-level
libraries? Maybe you have other things in mind.
Thanks,
Sébastien
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-devel-list
