Hi, On Mon, 01 Aug 2022, Chris Lamb wrote: > Regardless of that though, I think we have two options: > > a) Revert back to the 3.2.14 LTS version in Debian unstable. > > b) Wait for the 4.x stream to become designated LTS. I believe this > should happen with version 4.2, due for release in about 6 or 7 > months:
The Django and Debian releases are not well aligned. The 4.2 release is planned in April 2023 so a bit late given the freeze. If the number of reverse dependencies was lower, it could argued to try to have some sort of exceptions and offering extra work to help fix/migrate the reverse dependencies. But unfortunately I assume that most of the important reverse dependencies track mainly the LTS releases and the upstream fixes for 4.x compatibility will only materialize once Django 4.2 is released and we would have to commit to too much work to be able to push Django 4.x (including 4.2~rc1 or similar) in bookworn. As such, as much as I hate it, I think than only (a) is realistic. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hert...@debian.org> ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS
