Determine supported Oracle versions for Django 6.2 LTS

Django Internals
1

Oracle 19c and 21c will go end-of-life “out of order” because 21c is an “innovation release”, whereas 19c is LTS, see SupportedDatabaseVersions – Django.

@felixxm @nessita Do we generally drop support for end-of-life databases, even if “out of order”? 21c will go EOL a few months after Django 6.2 is released in April 2027.

Django 4.0 also encountered Oracle databases going EOL “out of order” but they were close enough in time that we could drop them together.

Where this came up concretely is on a ticket to add support for a feature available on Oracle 19.25+, but not on 21c. We could express this precisely, or we could take a decision first to drop 21c.

2

I think we should drop support for 19c and 21c, feel free to assign this ticket to me as we would need to do some OPS things to prepare a new CI setup.

2 Likes
3

Just wanted to clarify that the 26ai (there is no more 23ai nor 23c) follows directly 19c; they are both long term support release.

21c is an innovation release and has its own life (that will end by 31st July 2027), meaning its EOL doesn’t mean EOL of 19c (even if 19 < 21).

see https://www.oracle.com/us/assets/lifetime-support-technology-069183.pdf page 6