Date: Tue, 30 Dec 2025 12:35:26 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 291707] [META] Deprecate/Expire Django 4.2 and switch to Django 5.2 Message-ID: <bug-291707-21822-cadMZmdeQb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-291707-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291707 --- Comment #2 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=435163426e2dfb80c6a5d376d0c03075de700f19 commit 435163426e2dfb80c6a5d376d0c03075de700f19 Author: Kai Knoblich <kai@FreeBSD.org> AuthorDate: 2025-12-30 12:33:53 +0000 Commit: Kai Knoblich <kai@FreeBSD.org> CommitDate: 2025-12-30 12:33:53 +0000 www/py-django42: Deprecate/Set to expire * Set a deprecation note and let it expire to the end of May to give enough time to switch all affected ports over to Django 5.2 which is the next LTS release. The plan is to make every consumer ready for Django 5.2 during 2026Q1 and then switch everything to Django 5.2 after 2026Q2 has branched. PR: 291707 With hat: python Differential Revision: https://reviews.freebsd.org/D54248 www/py-django42/Makefile | 3 +++ 1 file changed, 3 insertions(+) -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291707-21822-cadMZmdeQb>