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: "Gabriel F. T. Gomes" <gabriel at inconstante dot eti dot br>
- To: Siddhesh Poyarekar <siddhesh at sourceware dot org>
- Cc: Florian Weimer <fweimer at redhat dot com>, "Andreas K. Huettel" <dilfridge at gentoo dot org>, <libc-alpha at sourceware dot org>, 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>, "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 11:14:52 -0300
- 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> <93d68f19-73a0-d906-ece2-bdc002507ca5@sourceware.org>
On 03 Oct 2017, Siddhesh Poyarekar wrote:
>On Tuesday 03 October 2017 12:52 AM, Florian Weimer wrote:
>>
>> 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.
If you actually agree to do one now, are we going to have something
similar to a code freeze? I'm asking because I believe some patches
should probably be considered release blockers, such as those in these
threads:
- https://sourceware.org/ml/libc-alpha/2017-09/msg00486.html
(already committed on the master branch)
- https://sourceware.org/ml/libc-alpha/2017-10/msg00102.html
(not yet on master, but probably relevant to the point-release)
Maybe there are more, and eventually others will emerge, so I have no idea
what criteria should be used to decide what goes in and what stays out of
this point release.
I agree that a targeted discussion about the need for a point release (as
you suggested) makes sense, but then it probably would also make sense to
discuss the relevance of particular patches as release blockers, which adds
to the work required for the release.