Re: New versioning scheme in gtk+. And in gtkmm?

[Chris Vine <chris cvine freeserve co uk>]

On Tue, 21 Mar 2017 17:22:58 +0100
Murray Cumming <murrayc murrayc com> wrote:
> On Sat, 2017-01-14 at 15:25 +0100, Murray Cumming wrote:
> > We might choose to wait a bit longer, letting us do another stable
> > glibmm and gtkmm release, maybe then changing the glibmm-2.52 ABI
> > name
> > to glibmm-2.54, for instance.  
>
> glibmm 2.52.0 has been released, but not GTK+ 4.0.0, so now is
> probably the time to do this.
>
> > I don't know when the GTK+ developers plan to call their GTK+-4.0
> > API stable, but it's obviously not going to be ready for the next
> > GNOME release in March 2017.
> >
> > There's no sign of a gtk-3-24 branch yet for GTK+, but we might
> > still release 3.24.* versions of gtkmm-3.0.
> >
> > Let's see how things develop over the next few weeks.  
>
> There's still no gtk+ 3.23/24, but we could still consider doing gtkmm
> 3.24/25. For now, I guess there is not a great demand for it.

It is possible I am wrong (the original naming proposals were changed
and I may have missed something) but I do not think there is ever
intended to be a 3.23/24.  As I understand it, 3.22 has become like
2.24: it will be maintained for some time - as a minimum 2 years - but
no new additions or changes of any kind (including CSS/theming and
gobject-introspection changes) will be made in the future.

I think it was intended to be 2 years before gtk+-4 comes out. In the
meantime gtk+-3.89/3.9* (the development series for gtk+-4) is supposed
to be in use by most gnome components during that period even though
API/ABI might change in it.  In fact nothing in gnome-3.23/3.24 uses it
(apart from gtkmm-3.89).  I can't say I am surprised.  No one
particularly likes to rewrite existing code and many gnome components
use functions deprecated in later versions of gtk+3 and removed from
gtk+-3.89.