glibc plans for 22.04 and kinetic

[Michael Hudson-Doyle]

On Thu, 30 Jun 2022 at 13:21, Robie Basak <robie.basak at ubuntu.com> wrote:

> Hi Michael,
>

Thanks for the reply!


> On Thu, Jun 30, 2022 at 12:43:20PM +1200, Michael Hudson-Doyle wrote:
> > I also want to get an SRU into jammy in time for the release of 20.04.1
> > which is due August 4, probably aiming for an upload some time next week.
>
> I assume you mean 22.04.1.
>
> Is there a particular reason this SRU needs to make 22.04.1? I ask
> because...
>

There are a couple of bugs we have been asked to fix before the point
release:

https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1971612
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1978130

There are about 25 other fixes from the upstream release branch I would
like in general terms to backport but we have not had requests to include
(and about 20 I do not want to include).


> > 2) Should I upload the fixes I intent to SRU to kinetic too? In general
> we
> > want fixes to go to devel first but glibc uploads are more disruptive
> than
> > most and kinetic will get the fixes anyway a few weeks later (all the
> > changes I have planned for SRU are backports). But if the release/SRU
> teams
> > would be happier with kinetic getting updated first, we can certainly do
> > that.
>
> Part of the reason we want things fixed in the development release first
> is to help find any issues to reduce regression risk for the stable
> release. When we rush to land a fix in an SRU that hasn't had widespread
> use elsewhere, we lose that opportunity. If there's a special reason we
> have to get a fix into 22.04.1 then maybe we need to compromise on that,
> but it seems to me that this would depend on the specifics.
>

Yeah, this is a fair point. In this case upstream has been somewhat looser
with putting things into the release branch than I would have been (and my
concerns are similar, for example there are performance improvements to
string functions in the release branch that have not been part of a glibc
release yet).


> I wondered if I was missing some routine thing that we've always done,
> but looking at the publication history of glibc, I don't see an SRU
> having landed prior to the first point release of Focal, Bionic or
> Xenial.
>

I have a general desire to be more proactive about bringing upstream fixes
to 22.04 LTS than we have been but perhaps aiming to get these fixes in
before .1 is not the best timing. Maybe I should make targeted fixes for .1
and aim to roll up more of the fixes from the release branch before .2 (at
least those that have been released as part of glibc 2.36 in kinetic).

Cheers,
mwh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-release/attachments/20220704/b642cfd1/attachment.html>