| From: |
| Siddhesh Poyarekar <siddhesh-AT-sourceware.org> |
| To: |
| Zack Weinberg <zackw-AT-panix.com>, "Yann E. MORIN" <yann.morin.1998-AT-free.fr> |
| Subject: |
| Re: Glibc stable release process (Glibc 2.26.1) |
| Date: |
| Sun, 1 Oct 2017 05:06:54 +0530 |
| Message-ID: |
| <5c98c67b-52a9-dcff-eda7-0f16b8ab478d@sourceware.org> |
| Cc: |
| Tulio Magno Quites Machado Filho <tuliom-AT-linux.vnet.ibm.com>, Romain Naour <romain.naour-AT-gmail.com>, "libc-alpha-AT-sourceware.org" <libc-alpha-AT-sourceware.org>, Joseph Myers <joseph-AT-codesourcery.com>, "Gabriel F. T. Gomes" <gabriel-AT-inconstante.eti.br>, Paul Eggert <eggert-AT-cs.ucla.edu>, Arjan van de Ven <arjan-AT-linux.intel.com> |
On Saturday 30 September 2017 05:27 PM, Zack Weinberg wrote:
> 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 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.
That is probably a waste of resources and also not entirely secure since
it would preclude signing packages.
As a past Fedora maintainer, the feedback I got from a number of package
maintainers and testers in the Fedora community was that it was easier
to bisect bad patches when they were backported piece by piece as
opposed to looking at two tarballs, getting their tags, downloading
upstream sources, making scratch packages for them and then running
tests on them. Given that Debian/Ubuntu follows a similar structure, I
suppose they would have similar problems.
That said, there seem to be at least 3 projects that seem to want this
(Gentoo, Clear Linux, Buildroot project) so I am inclined towards doing
a 2.26.1 point release for them unless anybody has a strong objection to
it. I'll set the release date to somewhere in the middle of October
(I'm flying back home to India from the US West Coast, so I'm likely
going to be in zombie state for a few days and fighting backlog) and
look to add the aarch64 falkor routines to it as well once they're reviewed.
Siddhesh
