Hi,
Noé Lopez via "Development of GNU Guix and the GNU System distribution." <[email protected]> writes: > Hi everyone, > > According to GCD 005, the first step towards a release in November¹ is > the nomination of a release team! > > We need one release manager with commit access and four other > people. If I am counting right, there is still not enough people. I can join the release team then, if I may. :) Have you guys already done something in the background, or is this thread all? I think there are two steps I see immediatelly: 1. There should probably be an issue that covers what happens when, according to the release schedule, so that it's easy for users & committers to track what they can expect, and what committers can/cannot do, ie. push major changes to master. This should probably also be announced on the mailing list. 2. There could be a milestone on codeberg, grouping the issue that need to be solved prior to the release. For example, right now there is this issue with libxml2 grafting that definitely needs to be resolved prior to the release. And this is pretty much 'blocked' by mesa-updates that currently has the 'ungrafting' job. I would also welcome this PR https://codeberg.org/guix/guix/pulls/2518 (I welcome other ideas of cuorse, but I really think this issue with online check should be resolved so that people can install even if CI frontend is down) Also, was it agreed who the release manager is? It's not clear to me from the e-mails. Regards, Rutherther
