Suggestion: Changes to release process, release from branch

Andreas K. Huettel dilfridge@gentoo.org
Fri Jul 31 14:36:32 GMT 2026


Am Montag, 27. Juli 2026, 21:58:18 Japanische Normalzeit schrieb Wilco Dijkstra:
> Hi Andreas,
> 
> > * No changes to the procedure during soft freeze and freeze, no changes to basic
> >  timetable
> >
> > * With the hard freeze two weeks before nominal/last possible release date, 
> >  the release branch is made, and the master branch is re-opened for development.
> 
> Would it make sense to make it ~4 weeks to give distros time to start testing and give
> feedback? It also leaves more time for important bugfixes. Given GLIBC is pretty stable
> most of the time (at least for the main targets), we could branch earlier.

I'm somewhat reluctant to extend the freeze timetable even more.

Keeping master and release branch in parallel for 2 weeks is no big deal, that's not
far away from what we are already doing now.

Anything (much) longer risks divergent commits...

> 
> Any fixes would first go into master for CI testing and then selected in the weekly
> meeting for an automated cherrypick into the release branch.
> 
> Cheers,
> Wilco
> 


-- 
PD Dr. Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, comrel, toolchain, base-system, perl, libreoffice)
https://wiki.gentoo.org/wiki/User:Dilfridge
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 870 bytes
Desc: This is a digitally signed message part.
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20260731/402f73f3/attachment.sig>


More information about the Libc-alpha mailing list