Hi, Noé Lopez via "Development of GNU Guix and the GNU System distribution." <[email protected]> writes:
> Hi everyone, > > Just a reminder that as of today, the toolchain and transition freeze is > active. Please do not push any changes that would cause major > transitions to master. > > Major updates to packages can still be pushed until December 1st with > some considerations: > > “Any change that alters a significant number of packages should be > carefully considered and updates that cause other packages to break > should be rejected.” > - GCD 005 > > You can still develop them on your team branches and keep them until > December 1st, when there will be a next-master branch that can receive > those changes. > > Thanks for your cooperation. I think I've already mentioned this before (during the GCD perhaps?), but why force everyone on a master-next branch when the release team (a smaller set of people) could instead branch current master into 'release-1.5.0' and issue a release from it, leaving the rest of the world continuing as normal? The release branch would accumulate a few commits, which would later be _merged_ into master at some points (_not_ rebased, to avoid rewriting them since the release tag would have been placed on a commit of that branch, which shouldn't change, e.g. for 'git describe' to print something sensical). -- Thanks, Maxim
