Opened 3 weeks ago

Closed 2 weeks ago

#37358 closed Cleanup/optimization (fixed)

Drop support for GDAL 3.3 and 3.4

Reported by: Jacob Walls Owned by: Jacob Walls
Component: GIS Version: dev
Severity: Normal Keywords: GDAL
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Jacob Walls)

GDAL 3.3 and 3.4 will be more than 5 years old when Django 6.2 is released in April 2027, and support for it can be dropped.

Previous ticket: #36756

Change History (7)

comment:1 by David Smith, 3 weeks ago

Triage Stage: Unreviewed → Accepted

comment:2 by Jacob Walls, 3 weeks ago

I think it's okay to drop 3.5 as well, which will be 4yr 11mo old in April 2027 (May 2027). 3.6.0 was yanked, so we could go to 3.6.1.

comment:3 by Jacob Walls, 3 weeks ago

Description: modified (diff)
Summary: Drop support for GDAL 3.3 and 3.4 → Drop support for GDAL 3.3, 3.4, and 3.5

comment:4 by Jacob Walls, 3 weeks ago

Description: modified (diff)
Summary: Drop support for GDAL 3.3, 3.4, and 3.5 → Drop support for GDAL 3.3 and 3.4

Never mind, I checked 5.2, which was the last time we had an April/May 4yr 11mo situation, and we didn't drop it, so I'll keep to the original scope. See #35776.

comment:5 by Jacob Walls, 3 weeks ago

Has patch: set

​PR

comment:6 by Jacob Walls, 2 weeks ago

Triage Stage: Accepted → Ready for checkin

Sarah approved on GitHub.

comment:7 by Jacob Walls <jacobtylerwalls@…>, 2 weeks ago

Resolution: → fixed
Status: assigned → closed

In 703283b:

Fixed #37358 -- Dropped support for GDAL 3.3 and 3.4.

Note: See TracTickets for help on using tickets.
Back to Top