Sorry if it was already discussed - I feel like it probably was, but can't see it right now.
Even though GTK+ has no plans for versions > 3.22, couldn't gtkmm branch and have an 'almost-stable' gtkmm-3-24, etc of its own for changes that are fairly innocuous, but which you still don't want in the 3-22 branch? It could be a bit confusing in terms of numbering, but as long as GTK+ keeps to its plan, never ambiguous with GTK+. Anyway, the potential for ambiguity could be sidestepped by using a different scheme, e.g. gtkmm-3-22-b, which would probably be sensible from the outset. The key thing, which might resolve the apparent concern, seems to be just using a different version number/name, to indicate to users that they have new or deprecated API to think about.
_______________________________________________ gtkmm-list mailing list gtkmm-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtkmm-list
