glibc release process

[Andreas K. Huettel]

Any more comments, objections, ideas, ...?

(In particular, for our rather manual QA in Gentoo the two-week phase
between branch and release is no problem, but can everyone else with their
fancy autobuilders handle this?)

If no objections I'd call for the soft/nominal freeze on 15/June.

Cheers -a

> Hi all, 
> 
> after taking care of the release process twice, I would like to suggest
> and put up for discussion some changes... The intention is to provide more
> time for the slow, old, and/or unusual architectures to do machine testing.
> Here we go.
> 
> 1) Nominal freeze: not 1 month but 6 weeks before release
> Mostly to accommodate the later changes, see below.
> Decision on what goes still in and what goes not, review and addition 
> of final patches.
> 
> 2) Machine testing: 1 month before release 
> Not, as currently, effectively 2 weeks before release (after waiting for
> the last important patches to go in)
> 
> 3) Branch: 2 weeks before release
> Master is opened for development
> Release branch only accepts obvious and simple bugfixes and/or fixes for
> issues found during machine testing
> 
> 4) Release: from release branch, not master
> 
> What do you think?
> 
> Cheers -a


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