Glibc stable release process (Glibc 2.26.1)

[Yann E. MORIN]

Zack, All,

On 2017-09-30 07:57 -0400, Zack Weinberg spake thusly:
> On Sat, Sep 30, 2017 at 6:18 AM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > What Romain and I were trying to say was that we would have to
> > arbitrarily choose the commit on the tree. That choice would look
> > random.
> >
> > Let's say that we decide to use today's last commit on the branch, which
> > is d37c951fde57e8acb320a9a7d437ba50a1fc3c8a. That's all good. But then
> > tomorrow, new commits get pushed to the maintenance branch, and now the
> > head of the same branch is 548cc83c38a91852b1e44045ead3d20ccd5db4cf
> > (it is now fdf58ebc60ce0eb459fd616241b52872b3571ac1; writing this mail
> > took much longer than I anticipated ;-] ).
> >
> > So in three days time, our "choice" would look no better as if we had
> > randomly choosen a commit on the tree. There is nothing that makes that
> > one stand out more than the ones before or after. Except that at some
> > point in time, it was the latest. But that is useless past that very
> > moment.
> [...]
> 
> I'm a little underslept and I'm not sure I fully understand the issue
> here, but would it help if we literally just tagged point releases and
> pushed tarballs to ftp.gnu.org from a cron job?  Once a month if there
> have been any patches since the previous tag, perhaps?

With my and Romain's Buildroot hats on, yes, that would be awesome! :-)

> With the
> official line being that all patches on the release branches are
> carefully vetted and we recommend tracking the git branch if you can,
> but this is easier for some downstream organizations so we offer this
> as well.

Totally in line with you on this.

Thank you! :-)

Regards,
Yann E. MORIN, Romain Naour.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'