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: Jonathan Nieder <jrnieder at gmail dot com>
- To: "Yann E. MORIN" <yann dot morin dot 1998 at free dot fr>
- Cc: Florian Weimer <fweimer at redhat dot com>, Siddhesh Poyarekar <siddhesh at gotplt dot org>, libc-alpha at sourceware dot org, Paul Eggert <eggert at cs dot ucla dot edu>, Zack Weinberg <zackw at panix dot com>, 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>, Arjan van de Ven <arjan at linux dot intel dot com>
- Date: Mon, 16 Oct 2017 10:52:16 -0700
- Subject: Re: Glibc stable release process (Glibc 2.26.1)
- Authentication-results: sourceware.org; auth=none
- References: <60f78cac-9cf4-51b1-9ade-21cd09783d96@gmail.com> <12f649be-94e4-eccb-be27-026119b7b431@cs.ucla.edu> <20171012192915.GF8813@altlinux.org> <3b29e10a-193a-8070-c040-2ceec9cc743c@redhat.com> <9e7b3052-2476-b6dc-6cff-6920828f3bbe@gotplt.org> <93677583-dc78-cb29-d9ea-d304e0922619@redhat.com> <20171016155520.GA2862@scaer> <34010cc9-62cb-ad22-1ff8-3c09ea59eee6@redhat.com> <20171016173456.GE2862@scaer>
Hi,
Yann E. MORIN wrote:
> The problem is not about representation of the version string. It is
> actually choosing what commit to use. As a downstream, we don't have
> many options when we need to choose a commit on the maintenance branch
> [1], i.e. either one of:
> - use the HEAD of the branch
> - use any one commit between the tag and the HEAD
>
> Let's say we choose HEAD now, and then tomorrow you push 5 new commits.
> Then the HEAD we choose today will tomorrow be seen just as randomly
> chosen as any other commit. It will tomorrow not mean much more than
> if we had clicked on the "I feel lucky" button then.
I don't really follow. Would the same problem exist when choosing
between 2.26.1, 2.26.2, 2.26.3, etc? Why isn't "use the latest
version from the branch" always the right answer?
> As a consequence, it is very difficult to express what glibc version is
> running on a system, because it would only ever report '2.26' (or am I
> mislead?),
Are you talking about version numbers from the package manager or from
somewhere else?
Thanks,
Jonathan