On Sun, 2026-11-01 at 20:33 +0100, Andreas Enge wrote: > Hello release team, > > thanks for the update! > > On Sun, Nov 01, 2026 at 07:58:58PM +0100, Noé Lopez wrote: > > A next-master branch will be created in a few weeks to host these > > changes. In the meanwhile, please keep them in your team branches. > > speaking of branches, there are a number of release* branches on CI: > https://ci.guix.gnu.org/ > Will you need any of these? If not, I can remove them, or we should > think about how to update them. For instance, edit the files > etc/manifests/release-*.scm. > > As far as toolchains are concerned, looking at the branches currently > queuing on QA, I suppose that python-team, ruby-team and haskell-team > count as frozen toolchain branches, while mesa-updates and gnome-team > can still be merged? This will also be important to know concerning > ungrafting commits, since I had suggested to piggy-back them on some > of these branches. > > Andreas
Hi Andreas, Yes, we need the release-* manifests. And they are in the process of being updated. The release-minimal and release-desktop manifests are packages used or installed by the installer, and our goal is that they build at 100%. They release-user-packages manifest is just a best- effort thing, for packages that are used by many people. For the freeze, I think your interpretation is right. I will add that its imperative that the ungrafting commits make it through, and they are not affected by the freeze. The plan is to have an ungrafting branch that can host those ungrafting commits that will not make it through.
