Page MenuHomeFreeBSD

www/py-django22: Deprecate and set to expire

Authored by kai on Jan 8 2022, 3:47 PM.
Referenced Files
Unknown Object (File)
Tue, Sep 12, 12:38 AM
Unknown Object (File)
Sat, Sep 9, 1:20 PM
Unknown Object (File)
Sat, Sep 2, 5:13 AM
Unknown Object (File)
Jul 8 2023, 10:19 PM
Unknown Object (File)
Jul 5 2023, 12:52 PM
Unknown Object (File)
Jul 3 2023, 12:04 AM
Unknown Object (File)
Jun 11 2023, 3:06 PM
Unknown Object (File)
Jun 4 2023, 1:25 PM


Django 2.2 will reach its End-of-Life in April 2022.

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

Test Plan
  1. Create a meta bug to track the whole progress
  2. Update as many ports during 2022Q1 but keep them assigned to Django 2.2
  3. Once 2022Q2 is branched, switch all those ports to Django 3.2
  4. Deprecate the py-dj32* ports as they are superfluous then
  5. If everything goes well Django 2.2 should be ready to be deorbited to the end of June 2022
  6. Plan B: Extend the deprecation date if some upstream repositories (e.g. Seahub) need a bit more time

See also:

Diff Detail

R11 FreeBSD ports repository
Lint Not Applicable
Tests Not Applicable

Event Timeline

kai requested review of this revision.Jan 8 2022, 3:47 PM
kai created this revision.
kai added a subscriber: koobs.

Reworded the deprecation note as suggested by @koobs .

dbaio added a subscriber: dbaio.

LGTM, it will give reasonable time for people to plan their Django upgrade.

This revision is now accepted and ready to land.Jan 17 2022, 8:46 PM
This revision was automatically updated to reflect the committed changes.