On Thu, 2019-09-12 at 08:19 -0500, mcatanz...@gnome.org wrote: > On Thu, Sep 12, 2019 at 2:45 AM, Milan Crha via desktop-devel-list > <desktop-devel-list@gnome.org> wrote: > > As a real life example, I skipped 3.32.5 this year, because there > > was > > no code change in the stable branch with which the users could > > benefit. > > The late stables are for bug fixes, from my point of view. > > I wondered about how to best present that on the schedule. > > We don't actually expect you to release tarballs past 3.34.0 unless > you > have actual need to do so (bugfixes that need released). These are > more > informational deadlines so that you know when our runtime updates > will > occur. > > E.g. say you release 3.34.0 on time, then by some magic nobody > reports > any bugs in evolution-data-server for four months. (Wouldn't that be > nice?) We make it to February and finally you have some fixes that > you > want to release. If you release your 3.34.1 by the tarball deadline > for > 3.34.5, then your 3.34.1 will make it into the 3.34.5 runtime update > during the next week. Otherwise it might wait six weeks until the > 3.34.6 runtime update. (We'll be doing 3.34 releases until March > next > year, because the runtime will be supported for one year. This > schedule > only shows the first half of the 3.34 lifetime.)
This is very important for the maintainers of libraries that live in the GNOME runtime. Do we have a full list of those? What happens if there are security issues that crop up in the meanwhile? _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
