Re: Planning for a release, for real

Hi, On jeu., 06 oct. 2022 at 16:50, Ludovic Courtès wrote: > • Update NEWS (mostly done already!), prepare a blog post listing the > highlights and linking to the relevant material. (See > for inspiration.) Just a reminder about ’guix

Re: Planning for a release, for real

It depends on the language, I'd say a week is good, maybe less as long as we can include a week-end (maybe it's personal, but I find more time to contribute in the week-ends). Le 7 octobre 2022 11:49:21 GMT+02:00, "Ludovic Courtès" a écrit : >Hi, > >Julien Lepiller skribis: > >> I'll take

Re: Planning for a release, for real

Hi, Christopher Baines skribis: > Ludovic Courtès writes: > >> We need to plan and coordinate. Releases have to be a group effort; >> some of the most important work won’t be coding but coordination. >> Coordination is key. I don’t think I should be spearheading that >> effort, but I’m happy

Re: Planning for a release, for real

On 07-10-2022 11:50, Ludovic Courtès wrote: Hi, Maxime Devos skribis: I have some unapplied security patches (from before the latest release (1.3.0) (!)) (more precisely, some patches that prepare for actually being able to write the security patches, once the preparation patches are

Re: Planning for a release, for real

Hi, Maxime Devos skribis: > I have some unapplied security patches (from before the latest release > (1.3.0) (!)) (more precisely, some patches that prepare for actually > being able to write the security patches, once the preparation patches > are merged, the actual security fixes should be

Re: Planning for a release, for real

Hi, Julien Lepiller skribis: > I'll take care of the cranslations (notifying translators, ensuring string > freeze is respected, …) Great, thanks. > We need to be careful not to start the stsing freeze step too early. Last > time (or previous?) we started a week before the scheduled release

Re: Planning for a release, for real

Ludovic Courtès writes: > We need to plan and coordinate. Releases have to be a group effort; > some of the most important work won’t be coding but coordination. > Coordination is key. I don’t think I should be spearheading that > effort, but I’m happy to be part of it. > > Who’s ready to

Re: Planning for a release, for real

On 06-10-2022 16:50, Ludovic Courtès wrote: Hello Guix! Will Guix’s 10th year be a release year? I hope so! We need to plan and coordinate. Releases have to be a group effort; some of the most important work won’t be coding but coordination. Coordination is key. I don’t think I should be

Re: Planning for a release, for real

I'll take care of the cranslations (notifying translators, ensuring string freeze is respected, …) We need to be careful not to start the stsing freeze step too early. Last time (or previous?) we started a week before the scheduled release date, but the schedule slipped by a few weeks and we

Planning for a release, for real

Hello Guix! Will Guix’s 10th year be a release year? I hope so! We need to plan and coordinate. Releases have to be a group effort; some of the most important work won’t be coding but coordination. Coordination is key. I don’t think I should be spearheading that effort, but I’m happy to be