Finalize release responsibilities for GNOME 40
Hi @akitouni @alatiera @jjardon @matthiasc,
It looks like I forgot to coordinate release responsibilities for GNOME 40 release cycle. Jordan and I will handle this weekend's releases. I have semi-arbitrarily assigned future releases to everyone to make this simple, but this is just a starting point. Please look over this schedule and feel free to swap with others, or request changes if I've given you a week you can't do:
- November 21
- 3.38.2: Michael
- 3.36.8: Jordan
- January 9
- 40.alpha: Jordan
- 3.38.3: Abderrahim
- 3.36.9: Matthias
- February 6
- 40.beta: Abderrahim
- 3.38.4: Matthias
- 3.36.10: Javier
- March 13
- 40.rc: Javier
- March 20
- 40.0: Matthias
- 3.38.5: Michael
- May 1
- 40.1: Abderrahim
- 3.38.6:
JordanMichael
(As usual, these dates are the tarball deadline, the weekend prior to release week.)
Note: we have 12 releases and 5 release engineers, so three of us will handle two releases, and two of us will handle three releases. For the 3.38 cycle, we had 17 releases, where Jordan, Javier, and I handled four releases, while Matthias and Abderrahim handled three releases. So this time, I've given Matthias and Abderrahim the extra third release. ;) I can't count properly. We have 13 releases and 5 release managers, so three of us do three releases, and two of us are lucky and have only two releases. Javier and Jordan will be lucky this cycle.
I also tried to split this up so we each do at most one devel release per cycle, since these are the hardest releases. I've also kept our established pattern where Abderrahim handles .90 (now beta), Javier handles .92 (now rc), and Matthias handles .0. Jordan has agreed to take alpha. This means Matthias and myself are spared the pain of regularly performing devel releases. (I can take backup duty when needed.)