Ludovic Courtès <l...@gnu.org> writes: > I believe what we need is a release team with rotating duties. That > is, a bunch of 3–5 people commit to doing the work leading to 1.5.0; > then a new team (possibly with overlap) takes over for the next > version, and so on.
The issue, as I see it, is the time commitment required from the release-team. Per doc/release.org: #+begin_quote The team has to be committed to be available for the duration of the whole process, which may typically span several weeks. #+end_quote For myself, while I do not have commit access, a several-week commitment with an unclear effort cap makes me hesitant. > As mentioned previously, I’m happy to mentor and help whoever steps > up. I know there are people up to the task; at least one person on the > team needs to have commit access, but apart from that, don’t be shy! Unless I am mistaken, at least one person on this list mentioned that they would be okay volunteering if the effort commitment could be reduced. Are you open to adapting the current release process (as documented in guix/maintenance.git) to reduce the manual effort? -- Suhail
