List view
The upcoming Leap 16 will come with Python 3.13 as default and so far does not seem to have Python 3.11 available in its default repositories. Moving to Python 3.13 thus needs to be in our sight. For this, however, we need to upgrade our Django version as our current (4.2) only supports up to Python 3.12. While support for Python 3.13 was added in Django 5.1.13, the latest Django series 5.2 is the latest LTS release and will thus receive security updates for at least 3 years (https://docs.djangoproject.com/en/5.2/releases/5.2/#django-5-2-release-notes). Upgrading to Django 5.2 should thus precede our move to Python 3.13 and this milestone will serve to centralize the required work.
No due date•5/9 issues closedUpgrade back-end tech to foster front-end modernisation. The 5.1.X-X Stable release milestone, in part, updated all back-end dependencies, but maintained the existing front-end support mechanisms. Build on these updates by enabling a more Django-native, where possible, front-end support structure. The prime directive here is to enable switch-out options for our ageing and burdensome JS dependencies. Along with the removal of all but the essential APIs required by, for example, replication. We have never had sufficient contributors to support such complexity. Ergo we pair down and focus on Django's modern options: which are now available to us; thanks to the last testing phase.
No due date•3/18 issues closed