Page MenuHomeFreeBSD

*: Switch consumers over to Django 4.2
ClosedPublic

Authored by kai on Apr 4 2024, 5:04 PM.
Tags
None
Referenced Files
F152592519: D44637.id137748.diff
Wed, Apr 15, 9:15 PM
F152583367: D44637.id137748.diff
Wed, Apr 15, 7:51 PM
F152495302: D44637.id137748.diff
Wed, Apr 15, 8:04 AM
Unknown Object (File)
Mon, Apr 13, 9:44 PM
Unknown Object (File)
Mon, Apr 13, 5:17 AM
Unknown Object (File)
Sun, Apr 12, 5:56 PM
Unknown Object (File)
Sun, Apr 12, 8:17 AM
Unknown Object (File)
Sat, Apr 11, 6:13 AM
Subscribers
None

Details

Summary
Django 3.2 become End-of-Life during April 2024 and Django 4.2 is the
new LTS (= Long Term Support) release which will be supported until
April 2026.

* Switch the most ports that use www/py-django32 to www/py-django42

* Ports that are not compatible with Django 3.2 have already been set
  with an expiration date were not taken into account.

* Bump PORTREVISION due dependency change where necessary.
Test Plan
  • poudriere -> OK (13.2-RELEASE amd64)
  • make index -> OK
  • As soon as this diff is committed (ETA around the end of April), the next step is to switch the consumer that are still using the py-dj42-* ports accordingly.

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kai requested review of this revision.Apr 4 2024, 5:04 PM
kai created this revision.

Parts that affect me look good

This revision is now accepted and ready to land.Apr 7 2024, 11:04 AM

Same, Seahub supports Django 4.2 along with the other depends under my care.

I'm working in-house to get the devs to confirm security/py-first-server is good with Django 4.2

This revision was automatically updated to reflect the committed changes.

Committed, thank you for your time and feedback, @dvl , @grembo and @ultima!