Change Details

# Create a meta bug to track the whole progress # Update as many ports during 2024Q1 but keep them assigned to Django 3.2 # Once 2024Q2 is branched, switch all those ports to Django 4.2 # Deprecate the py-dj42* ports as they are superfluous then # If everything goes well, Django 3.2 should be ready to be deorbited to the end of June 2024 # Plan B: Extend the deprecation date if some upstream repositories (e.g. for www/py-horizon) need a bit more time See also: https://wiki.freebsd.org/Ports/Django/Django42Migration

# Update as many ports during 2024Q1 but keep them assigned to Django 3.2 # Once 2024Q2 is branched, switch all those ports to Django 4.2 # Deprecate the py-dj42* ports as they are superfluous then # If everything goes well, Django 3.2 should be ready to be deorbited to the end of June 2024 # Plan B: Extend the deprecation date if some upstream repositories (e.g. for www/py-horizon) need a bit more time See also: https://wiki.freebsd.org/Ports/Django/Django42Migration

# Create a meta bug to track the whole progress # Update as many ports during 2024Q1 but keep them assigned to Django 3.2 # Once 2024Q2 is branched, switch all those ports to Django 4.2 # Deprecate the py-dj42* ports as they are superfluous then # If everything goes well, Django 3.2 should be ready to be deorbited to the end of June 2024 # Plan B: Extend the deprecation date if some upstream repositories (e.g. for www/py-horizon) need a bit more time See also: https://wiki.freebsd.org/Ports/Django/Django42Migration