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

[Carlos O'Donell]

Community,

In a recent Monday Patch Queue review meeting a suggestion was raised
by Adhemerval to try doing more detailed plans for the glibc releases.

The benefits of a detailed plan for a 6-month development cycle
would be that it allows reviewers to support patch review for the
committed plan.

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

We already had a "Planning" section in the release template page
so I'm suggesting we reuse that section and plan against the months:

https://sourceware.org/glibc/wiki/Release/2.40#Planning

I have added 2 things I'd like to see this release and put them against
February and April. My goal is to commit to these two items and support
getting them completed in that month. If they aren't complete then we
can re-evaluate. Development should proceed as normal but during patch
queue review I will give priority to the items in the plan and seek
reviewers for those items to attempt to complete the review (similar to
how we handle blockers in Month 6).

I don't want to define a complex process here. If there is something that
you would like to see happen then add it to the plan and if a given month
gets too busy then we'll discuss it as a community.

Please add items to the plan :-)

Thoughts?

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

-- 
Cheers,
Carlos.