-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Mon, 2019-11-11 at 10:33 +0100, Ondřej Nový wrote:
We are going to raise the severity of the py2removal bugs to "serious"
in several steps. In the
first phase we are going to raise severity of the py2removal bugs for
all leaf module packages and low popcon (< 300) application packages.
Bugs marked with the "py2keep" user tag will not have their severity
raised. If nobody fixes that bug, the packages will be auto-removed
from testing.
We will also then file bug reports against ftp.debian.org to remove
such packages from unstable. We are going to do this semi-
automatically as additional packages become leaf packages.
Hi,
sorry if this has been discussed already somewhere else (I stopped reading
- -devel@ a long time ago) but is there something done to improve NEW processing
here? I have two package sitting there because of the introduction of a
- -python3 binary package. I don't think it's really make sense to remove
python2 stuff if python3 stuff can't enter the archive…