Glibc stable release process (Glibc 2.26.1)

[Florian Weimer]

On 10/16/2017 05:55 PM, Yann E. MORIN wrote:
> Hello All! :-)
> 
> On 2017-10-16 15:20 +0200, Florian Weimer spake thusly:
>> On 10/16/2017 02:48 PM, Siddhesh Poyarekar wrote:
>>> On Friday 13 October 2017 01:29 AM, Florian Weimer wrote:
>>>> If you don't see a problem with that, I'm going to suggest this on a
>>>> separate thread (it's too buried here to receive proper attention).
>>>
>>> This is a good idea in general and a trivial point to add to the release
>>> process.  Do you intend to propose this as a full replacement for point
>>> releases (i.e. never do it) or just an added convenience for those who
>>> don't care for point releases or a fallback for when the release manager
>>> (or one of the package signers, i.e. Carlos, Joseph, me, etc.) does not
>>> want to spend time on a point release?
>>
>> I think it's a sufficient replacement for point releases, but I suppose
>> others will disagree.
> 
> Well, I won't re-hash the explanations I expressed, but I'll just state
> that a point-release would be better, IMHO. It is not necessary to put
> out tarballs, though; a tag would be enough.

Why do you think a tag would be superior to the output from “git 
describe”?  Because we can change it subsequently to point something else?

Thanks,
Florian