Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Nicholas D Steeves Newsgroups: linux.debian.maint.python,linux.debian.devel.release Subject: Re: Python 3.11 for bookworm? Date: Thu, 22 Dec 2022 02:30:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Dec 22 01:21:38 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-115.024 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.515, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Debian-User: sten X-Mailing-List: archive/latest/20639 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/87ili4jksa.fsf@DigitalMercury.freeddns.org Approved: robomod@news.nic.it Lines: 71 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Wed, 21 Dec 2022 20:21:09 -0500 X-Original-Message-ID: <87ili4jksa.fsf@DigitalMercury.freeddns.org> X-Original-References: <1fc30086-582e-36e1-f530-39323e85cd8d@ubuntu.com> Xref: csiph.com linux.debian.maint.python:14771 linux.debian.devel.release:112524 --=-=-= Content-Type: text/plain Sandro Tosi writes: > thoughts from a concerned maintainer > Sandro, thank you for writing this email. > > it seems this email advocates for a "let's wing it"[1] type of transition. > > [1] https://en.wiktionary.org/wiki/wing_it > > It appears there has been little work in preparing the work to > introduce python3.11 from its maintainer, instead that works has been > pushed downstream to maintainers. > > if we continue with the plan as described above, several python > libraries/applications maintainers will be left with the short end of > the stick and deal with an unknown amount of issues (upstream fixes > not available, not ready and or/ not released, rushed, etc) with less > than a month from the beginning of the transition freeze[2] > Agreed. At a bare minimum, complete data from ratt (Rebuild All The Things) should be required at this point. > [2] https://release.debian.org/bullseye/freeze_policy.html > > [2] also highlights at the very beginning "Plan your changes for > bullseye", this change appears as if it was not planned and we should > be skeptical to proceed without further (and in advance) understanding > of the impact it may have on Bullseye. > 100% +1 I'm especially concerned about how a clear plan was not communicated to other teams--whose work will be broken by the proposed transition, were an exception to be granted. Debian is not a paragon of community if it makes late, unannounced changes that result in a yet-undetermined number of projects being dropped from bookworm's release. If Python 3.11 as the only supported version is a release goal, then the freeze schedule would need to be modified. Regards, Nicholas --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJEBAEBCgAuFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmOjsQUQHHN0ZW5AZGVi aWFuLm9yZwAKCRBaiDBHX30QYfLpEAChdtXyXOLR+P/cdNXtzQdfsujiPj+taAXA 8VxiYzmklX5ehX2b1awsAMFuZtFFIiGwu3J2YwoYrkKeVC2+5KRA/PRVZmP/c8+c zDUQ3hqosXbUY8SfzpN3KwPYsTPmBWq/jUbTxSfqBSi76Xy58OnkHkLBQ+TrPSjF s+vtkbTgFjIR5ThT2EEgU8BkCG6ycsw5mbrMq80Ld9GjAo+twczx6jEuN+lKEaR7 OEDn6DBgVp+my6lGjkovOB8vAoo7THv8BZndwH1+YEGPAzusqxFEoRNvLKF/XfqR RM7OJqHxwVlts8PxXx8vQhlUUJ5Ff5oiVWVvKPtomneLu5JfFYzoLZlbcOy17MuM GkjEXVP7y1rrX2PR+rjcpF9lIpuKNEO5Nkxi5AXmv1Yt388g9ZbJd1bGqIeF/+sm OofFRu5xqBt3yo3Qf1bCHQ+r7VfB8pj4kDqC/ctweQolJLaCdpJx7uKeLwUzQfo0 nouM78ewgouiQLYCxV5P8wj3Jo4olR3Ev/ir08QLXM3s2uOSca86cziATxM6Bhf3 0Ubu4MHpYK1xsrNeQvpLzyUMCrrce/AIUb9Py434SrYtfqc3spR6nPgx/vpSyYB6 +TS6NlELsv/3C86+vwTpcAeqRRvbudqGhrU1jJ2Zf3Wj/GcxlMfthR3r2ew3EInz +Z7AE9iXAg== =fezG -----END PGP SIGNATURE----- --=-=-=--