Re: 3.33/3.34 schedule draft: questions
- From: mcatanzaro gnome org
- To: Andre Klapper <ak-47 gmx net>
- Cc: release-team gnome org
- Subject: Re: 3.33/3.34 schedule draft: questions
- Date: Fri, 08 Mar 2019 10:40:29 -0600
On Fri, Mar 8, 2019 at 3:34 AM, Andre Klapper <ak-47 gmx net> wrote:
I've put up a draft schedule at
https://wiki.gnome.org/ThreePointThirtythree and in
https://gitlab.gnome.org/GNOME/releng/commit/6ff90169cc36f0793beaf27fde629cc7118eee6f
Problem: GUADEC is very late (end of August) and 3.34 release should
be
in early September. On the other hand, anyone can branch gnome-3-34
from master early and still hack away on master?
Not sure how many people will be happy to create .92 tarballs while
being at GUADEC (and someone to do the release)? If you think it's no
problem to have the .92 at GUADEC then I'm happy to make the hardcode
freeze again only one week (currently two weeks) and have a .4 release
again (I currently went only for 3 unstable releases before .90 comes)
I recommend we avoid having any sort of release week during GUADEC, so
glad your schedule avoids that. But having two weeks between .92 and
the final release doesn't seem great, either. And code freeze during
GUADEC seems likely to, er, stress our collective willpower.
We could move the 3.34.0 release back one week, to September 11. Then
we could have:
* 3.33.90: August 5-7
* 3.33.91: August 19-21
* GUADEC: August 23-28
* 3.33.92: September 2-4
* 3.34.0: September 9-11
That's one week harder for Ubuntu, but it avoids any conflict with
GUADEC, and is actually more in line with our traditional schedule. (I
believe we traditionally targeted the third week of the month.)
Targeting the first week of March and September is definitely better
for Ubuntu and Fedora, and I hope we can try to do that again in the
future (we did for 3.30 but not for 3.32), but due to GUADEC it just
doesn't work well for 3.34.
Michael
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]