Re: Bits from the Release Team (Jessie freeze info)
- To: debian-devel <firstname.lastname@example.org>
- Subject: Re: Bits from the Release Team (Jessie freeze info)
- From: Bernd Zeimetz <email@example.com>
- Date: Sun, 13 Oct 2013 19:41:15 +0200
- Message-id: <[🔎] 525ADB3B.firstname.lastname@example.org>
- In-reply-to: <20131013150131.BBDEB2000C2F8@thykier.net>
- References: <20131013150131.BBDEB2000C2F8@thykier.net>
-----BEGIN PGP SIGNED MESSAGE-----
> We are happy to announce that we will freeze Jessie at 23:59 UTC on the 5th
> of November 2014.
thanks for annoucing that early and for your work!
> [...] * Proactive automated removals 3 months into the freeze. - Note that
> bug-free packages will be removed if they (build-)depend on a RC-buggy,
> non-key package.
Could we get a warning about such removals before they are scheduled? Like at
least one week before? Having an eye on all packages all my packages
build-depend is something which would be great to avoid ;)
> - Native packages are at a disadvantage here, since all uploads of native
> packages are considered a new "upstream" version.
So whats the "fix" for that? Migrating native packages to non-native ones does
not always make sense.
> [...] - It should also go without saying that embedding a new upstream
> release in a patch just to get a such "carte blanche" exception is also
> considered abuse.
What about bugfix point-releases from upstream, like postgres and other sane
upstreams do it?
thanks & cheers,
Bernd Zeimetz Debian GNU/Linux Developer
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
-----END PGP SIGNATURE-----