On Wed, 2007-04-18 at 11:42 -0600, Elijah Newren wrote: > Hi all, > > So I was trying to improve our release documentation by coming up with > a list of modules in official GNOME release sets that do not follow > the GNOME release cycle, such as gtk+. We have discouraged adding > such modules as time has gone on, but there are still lots of existing > modules like this from 2.0 and early 2.x days. Problem is, I wasn't > around for all the discussions way back then, and I really don't know > the state of all modules (nor even all the reasons for this > splitting). > > It'd be really helpful if people could read over my initial draft and > provide corrections and clarifications: > > http://live.gnome.org/ReleasePlanning/SeparateReleaseCycleModules
glibmm and gtkmm follow glib and GTK+ release cycles and version numbers. I'd like to follow GNOME's faster cycle, so I can add API without adding it in, e.g., 2.10.5, but I don't want the version numbers to get out of sync. Likewise libglade(mm). The rest of the *mm modules follow GNOME's cycle because the underlying C libraries do. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
