Hi Holger! Holger Levsen <hol...@layer-acht.org> writes:
> hi, > > debian-security-support | 2019.12.12~deb8u2 | jessie-security | > source, all > debian-security-support | 2020.06.21~deb9u1 | stretch | > source, all > debian-security-support | 2020.06.21~deb10u1 | buster | > source, all > debian-security-support | 2020.07.12 | bullseye | > source, all > debian-security-support | 2020.07.12 | sid | > source, all > > is what we currently have in the archive and which is a bit of a hassle to > maintain due to keeping version constraints sane (=newer releases should > always > have higher versions) and since rather frequently there are changes only > affecting older releases (so one has to upload to sid first, then do a stable > update and then update oldstable to propagate something which is only relevant > for oldstable atm.) > > Hence I propose to bump the epoch and introduce this versioning scheme: > > sid: 0:11~2020.08.17 > bullseye: 0:11~2020.08.17 > buster: 0:10~2020.08.17 > stretch: 0:9~2020.08.17 > and so on. > This makes sense to me, because with this motion the debian-security-support package would provide admins with notifications about known issues faster (presumably providing them with the information they need to possibly opt-in to a manual early update for an affected package). The potential risks of increased package mobility seem negligible to me, because this package doesn't patch any other software. I hope this is the case, and that all that is needed is a release team ack :-) Cheers, Nicholas
signature.asc
Description: PGP signature
