[Bug 276319] [META] Deprecate/Expire Django 3.2 and switch to Django 4.2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276319

--- Comment #1 from commit-hook@FreeBSD.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/ports/commit/?id=3687e17c78a7df3ec9f510a89cab232effdaab51

commit 3687e17c78a7df3ec9f510a89cab232effdaab51
Author:     Kai Knoblich <kai@FreeBSD.org>
AuthorDate: 2024-01-16 05:12:41 +0000
Commit:     Kai Knoblich <kai@FreeBSD.org>
CommitDate: 2024-01-16 05:12:41 +0000

    www/py-django32: Deprecate/Set to expire

    * Set a deprecation note and let it expire to the end of June to give
      enough time to switch all affected ports over to Django 4.2 which is
      the next LTS release.

      The plan is to make every consumer ready for Django 4.2 during 2024Q1
      and then switch everything to Django 4.2 after 2024Q2 has branched.

    PR:             276319
    Differential Revision:  https://reviews.freebsd.org/D43344
    With hat:       python

 www/py-django32/Makefile | 3 +++
 1 file changed, 3 insertions(+)

-- 
You are receiving this mail because:
You are the assignee for the bug.