Hi, On Sun, May 31, 2026 at 05:04:24PM +0200, Rutherther wrote: (...) > And it had seemed likely the > core-packages-team would fall to the freeze period. I am not sure what > the current state of core-packages-team is, but I believe it would be > nice to coordinate with them. Both due to the team having effect on > everything in Guix, and because it would be nice to have more up to date > coreutils and so on. If the team merge falled into the freeze period, I > am afraid the core packages team could face a lot of trouble waiting for > being able to merge to master, facing a lot of conflicts / build > failures. This of course can affect also other teams, but to me it seems > the order of magnitude is lower (or does someone disagree with this? I > do not have that much insight into this, so this is just naively > building on the fact that everything in Guix depends on it) (...)
Yeah, this would be great. I'm personally interested in some work that would unlock Perl being merged: that would let us ship a maintained Perl and update libraries. (...) > I believe that next year the schedule could then be followed, having a > release in June, as proposed by the GCD. > > I am still pending to submit some changes to the release process repo, > https://codeberg.org/guix/release-planning/pulls/7, and I am sorry I > haven't done it yet. I am extremely busy with work at the moment, > chasing features to release elsewhere than Guix :) (...) You and Noe really carried the torch for the last release, I hope we can continue to find people that want to help and that we can make it easier/better each time. Steve / Futurile
