On Sun, Dec 15, 2024 at 03:21:44PM -0500, Suhail Singh wrote: > Ricardo Wurmus <[email protected]> writes: > > > Efraim Flashner <[email protected]> writes: > > > >> Since, IMO, the major uses of the actual guix package is for the daemon > >> and the installer, I think we could tag a minor release just about every > >> time we bump the guix package. > > That's a sensible approach. How should the discussion proceed further? > Do we have a proxy to determine whether everyone who needs to be > involved for consensus-based decision-making has weighed in?
I'd argue that cutting releases is one of those specifically maintainer duties but I'd love to hear from other people who disagree. If we do consider the daemon and installer the main reason to actually cut a release, then I'd argue the daemon always works (we'd know otherwise), I think we have an installer team, and we should probably get some feedback from the desktop teams to make sure everything seems to be working well enough. I have some opinions about our aarch64 based images, but that should be a separate email. > > I've only ever signed off on one release (0.13.0?) and I'd be happy to > > help get another one out of the door. > > What does making a release entail? Is this documented somewhere? > > -- > Suhail -- Efraim Flashner <[email protected]> אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted
signature.asc
Description: PGP signature
