Re: Planning for glibc releases --- What should go into glibc 2.40?

["Andreas K. Huettel" <dilfridge@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]

> In a recent Monday Patch Queue review meeting a suggestion was raised
> by Adhemerval to try doing more detailed plans for the glibc releases.
[...]
> We do something similar as we approach the end of the development
> cycle by recording blockers in the release wiki and then reviewing
> and making progress on the blockers.
> 
> The goal would be to do something similar but on a monthly cadence.
> 
> For example:
> 
> Month 1 - Feature 1
> Month 2 - Fix 2
> Month 3 - Enhancement 3
> Month 4 - Hardware Enablement 4
> Month 5 - Feature 5
> Month 6 - Blockers
> 

It's worth trying. 

I mean, the effect of the freeze is usually that there's a bunch of
features going in at the last moment, leading to testing and fixing...
If we can distribute that better over the development period that
would be great.

How about a "halfway tag" on master after ~3 months, maybe 
accompanied by tarballs, as reference if anyone wants to do machine
testing?
(The mips-o32 clone3 patch was in very early...)
Not as "release" in any way, none of the "release guarantees", but 
we could at least try to have patchsets / groups of features complete
before.

> I'm particularly keen to hear if the distributions have any features,
> fixes, or enhancements they want to see completed.

BZ #23960 (yes I know I'm nagging :o), and sorry I dont remember
offhand what the latest state was), BZ #24050

Cheers,
Andreas

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]