4 ms·
So this is an ass backwards way of saying that GTK releases are going to be in beta for 2 years and the real releases are going to be called gtk4.12 instead of
by Avshalom 10y ago
So this is an ass backwards way of saying that GTK releases are going to be in beta for 2 years and the real releases are going to be called gtk4.12 instead of gtk4
On one hand okay fine. On the other hand this is ass backwards: just admit you're doing beta releases.
- megous 10y agoNo. What it seems like is that they want more flexibility while developing GNOME (6 month cycle as it is now), and provide some stability for outside users of GTK+ too (2 year cycle). Beta releases are done within the regular 6 month cycle.
- digi_owl 10y agoThen they should just fork GTK and be done with it. Or write a layer between GTK and Gnome, like there appears to be between KDE and Qt.
- audidude 10y agoIf GNOME forked GTK, there would no longer be a GTK.
- digi_owl 10y agoI could have sworn GTK existed before Gnome. Surely it can exist after as well...
- audidude 10y agoYou are likely miss-remembering. The extraction of the toolkit from GIMP was done as the early pioneering of GNOME. Before that, it wasn't really a toolkit. I mean, it was an in-application toolkit, but that is very different from a usable toolkit.
- megous 10y agoPerhaps the authors of the toolkit are better positioned to judge what the release policy and development approach should be. They take long term stability requirement of outside parties into account with this new approach. I'm not sure why they couldn't use the benefit of being in control of the toolkit while developing GNOME, and write some adapter layer, like KDE.