This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Glibc stable release process (Glibc 2.26.1)


Siddhesh Poyarekar wrote:

> Agreed and most users don't even look at the packages, they look at
> release notes.  I was referring to the QE teams and their convenience of
> backing out individual patches in the spec file as opposed to figuring
> out bisecting patches in git.  They're much more comfortable doing the
> former since that is what they do all the time for all packages.

FWIW this is not true in Debian.  It sounds like it's mostly a Red Hat
specific thing.

Debian follows stable branches for some packages (e.g., Linux) and
does not for some others (e.g., Git).  It comes down to how close
upstream is to Debian's point of view on which patches are important
enough to apply to the stable branch.

I don't know where glibc falls on that spectrum.  It may be that
Debian would be able to consume glibc point releases as updates to an
already released Debian release.  It's likely that Debian wouldn't.
(That said, I am not saying tagged point releases would *hurt* Debian
--- this reply is only about the question of whether they would help.)

Thanks,
Jonathan


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]