Glibc stable release process (Glibc 2.26.1)

[Siddhesh Poyarekar]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tuesday 03 October 2017 08:27 PM, Andreas K. Huettel wrote:
> Given that your previous recommendation was "stay with the tip of
> the release branch", that sounds unnecessary. My recommendation
> from my experience as packager of other software would be, * keep
> adding backports to the release branches as careful as now * tag
> (and tar?) point releases from the release branches at regular 
> intervals, say every two months. This might make releases more
> comparable between distributions.

I think the difference there is on who has the responsibility of
testing the release tarball.  When we bless a release as upstream, we
should at least be doing some minimal testing before throwing it over
the wall.  If a distribution builds a tarball off the branch and uses
it, it becomes their responsibility to test :)

Siddhesh
-----BEGIN PGP SIGNATURE-----

iQFMBAEBCAA2FiEEvHxzcmN+wQxX16plecQ9+/HPIYcFAlnUgQUYHHNpZGRoZXNo
QHNvdXJjZXdhcmUub3JnAAoJEHnEPfvxzyGHp5EH/1I+8s2iPlltknhLsxYrxC9c
THAijpZs8yr+vBat+T8MsfTxN92YDbxGTPH3yQuU5riThJs0q6DGNj+MIKBA76ZI
zzZeXav3yCHRMm/WIRp0kysUHhnXj3GB976nJart2HjcrZEgYdPQok50/Xdhd4po
8ORMcST0g2lSnHltAX5fEcj51W1N57Av3ykdNJdaSLS2PELC0e3mWJb0zEcNUm+l
PmWN37IlY0lxCKPMhHrndafSIEQ2Thk36bMIq0dKDEF5hHrDl0MXWtyVNW0wsmLL
oi0cgfThzmD9k2UYleut/+IMFgOeB6YxgXppfi3RYuJd4vJLCkZ6yXVM2KdKZ+Q=
=MdDO
-----END PGP SIGNATURE-----