This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Glibc stable release process (Glibc 2.26.1)
- From: Siddhesh Poyarekar <siddhesh at sourceware dot org>
- To: Florian Weimer <fweimer at redhat dot com>, "Andreas K. Huettel" <dilfridge at gentoo dot org>, libc-alpha at sourceware dot org
- Cc: Zack Weinberg <zackw at panix dot com>, "Yann E. MORIN" <yann dot morin dot 1998 at free dot fr>, Tulio Magno Quites Machado Filho <tuliom at linux dot vnet dot ibm dot com>, Romain Naour <romain dot naour at gmail dot com>, Joseph Myers <joseph at codesourcery dot com>, "Gabriel F. T. Gomes" <gabriel at inconstante dot eti dot br>, Paul Eggert <eggert at cs dot ucla dot edu>, Arjan van de Ven <arjan at linux dot intel dot com>
- Date: Tue, 3 Oct 2017 10:23:57 +0530
- Subject: Re: Glibc stable release process (Glibc 2.26.1)
- Authentication-results: sourceware.org; auth=none
- References: <60f78cac-9cf4-51b1-9ade-21cd09783d96@gmail.com> <CAKCAbMj3ByTofE=WsKV-SXOCWyJYStRKvP3DA9ttiW2hUNZffA@mail.gmail.com> <5c98c67b-52a9-dcff-eda7-0f16b8ab478d@sourceware.org> <2839686.ckfu0BZrXq@porto> <a30cc34e-f71f-8e8a-1b99-1c3c1b798e84@redhat.com>
- Reply-to: siddhesh at sourceware dot org
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