Glibc stable release process (Glibc 2.26.1)

[Siddhesh Poyarekar]

On Tuesday 03 October 2017 12:52 AM, Florian Weimer wrote:
> We continuously rebase Fedora on top of the upstream stable release
> branch for that Fedora release (but we do not switch branches within a
> release).

Interesting that the Fedora community actually agreed to do that because
there was a significant amount of flaming in the past due to this very
reason.

> I still don't understand why you need tarballs for releases, though.  or
> put differently, the difference between glibc 2.26.5 and glibc 2.26-40
> seems rather minor to me, and producing the tarballs is quite a bit of
> work for us.

Right.  To be clear, even if I agree to do one now, it should not be
binding on any future release managers to do the same for their release
branch.  Maybe it makes sense to have a targeted discussion like this
with the final decision being that of the release manager for that release.

Siddhesh