Glibc stable release process (Glibc 2.26.1)

[Andreas K. Huettel]

Am Samstag, 30. September 2017, 13:57:55 CEST schrieb Zack Weinberg:
> [...]
> 
> 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.

Yes please!!!

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20170930/e716b17e/attachment.sig>