Hello, Noé Lopez <[email protected]> skribis:
> This week was the preparations for the release candidate, which we had > set a target for today. However some more work needed to be done and the > release candidate is not yet ready. We will aim to release it before > Christmas. > > The ungrafting branch was merged thanks to the help of many people > outside of the release team. Thanks! > > We have managed to make AArch64 release artefacts bootable on real > hardware! Congrats to the team and everyone who helped! I had to check how “hard freeze” is defined in the GCD¹: ## Testing and Hard Freeze (week 10) Release Crictical (RC) bugs and issues should be solved for the release branch. Only changes that will fix a non-building package, or a RC bug in a package/service are allowed. Ideally avoid new upstream versions, but it's acceptable to use a new minor upstream version to solve a bug. Any non-building packages are deprecated using the Deprecation Policy. As always, packages can be un-deprecated at a later date. I think we contributors might need to solicit you, release team, to determine whether a given bug is “release critical”, for the non-obvious cases. Ludo’. ¹ https://consensus.guix.gnu.org/gcd/005-regular-releases.html
