Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Ondrej Novy <novy@ondrej.org>
Newsgroups: linux.debian.maint.python
Subject: Re: Discussing next steps for the Python2 removal
Date: Thu, 24 Oct 2019 22:10:01 +0200
Message-ID: <yURAJ-8kE-7@gated-at.bofh.it>
References: <yU3Xk-1fZ-19@gated-at.bofh.it>
Old-Return-Path: <ondrej.novy@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0000000000006222df0595ad63ae"
Approved: robomod@news.nic.it
Lines: 69
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:11935

--0000000000006222df0595ad63ae
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

notes from this meeting (
https://gobby.debian.org/export/Teams/Python/Py2Removal):

We want to bump all bugs to RC bugs, if they are:
* leaf package
* with py2 binary
* bug is not marked as py2keep
* all modules and low popcon apps (< 300)

If package will be removed from testing (auto-rm), we are going to remove
them from unstable. We are going to run this process semi-automatically
(after more packages gets leaf). First version of list should be checked
(emailed to this ML). We need to prepare draft of RC-bumper email.

We will send email to d-d-a with current state, our next steps, etc.

We are going to bump Lintian tags severity:
* python-foo-but-no-python3-foo: warning->error
* dependency-on-python-version-marked-for-end-of-life: pedantic->warning
* new-package-should-not-package-python2-module: warning->error
* build-depends-on-python-sphinx-only: warning->error
* depends-on-python2-and-python3: info->warning
* script-uses-unversioned-python-in-shebang: info->warning

We would like to update Python policy and clearly state future of Python 2.

Thanks everybody.

--=20
Best regards
 Ond=C5=99ej Nov=C3=BD

--0000000000006222df0595ad63ae
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><div><br></div><div>notes from this meeting =
(<a href=3D"https://gobby.debian.org/export/Teams/Python/Py2Removal">https:=
//gobby.debian.org/export/Teams/Python/Py2Removal</a>):</div><div><br></div=
><div>We want to bump all bugs to RC bugs, if they are:</div>* leaf package=
<br>* with py2 binary<br>* bug is not marked as py2keep<br>* all modules an=
d low popcon apps (&lt; 300)<div><br></div><div>If package will be removed =
from testing (auto-rm), we are going to remove them from unstable. We are g=
oing to run this process semi-automatically (after more packages gets leaf)=
. First version of list should be checked (emailed to this ML). We need to =
prepare draft of RC-bumper email.</div><div><br></div><div>We will send ema=
il to d-d-a with current state, our next steps, etc.</div><div><br></div><d=
iv>We are going to bump Lintian tags severity:</div><div>* python-foo-but-n=
o-python3-foo: warning-&gt;error<br>* dependency-on-python-version-marked-f=
or-end-of-life: pedantic-&gt;warning<br>* new-package-should-not-package-py=
thon2-module: warning-&gt;error<br>* build-depends-on-python-sphinx-only: w=
arning-&gt;error<br>* depends-on-python2-and-python3: info-&gt;warning<br>*=
 script-uses-unversioned-python-in-shebang: info-&gt;warning<br></div><div>=
<div><br></div><div>We would like to update Python policy and clearly state=
 future of Python 2.</div><div><br></div><div>Thanks everybody.</div><div><=
br></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"=
><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><di=
v dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div>Best regards=
<br>=C2=A0Ond=C5=99ej Nov=C3=BD<br></div><div><br></div></div></div></div><=
/div></div></div></div></div></div></div></div></div></div></div></div></di=
v>

--0000000000006222df0595ad63ae--