Indeed, we started bumping MAJOR version due to dropping py27 support. Though, the rule is, that a change in required package's version, only warrants a MINOR version bump. But python is not just a simple dependency, and dropping support of a python version is more than just bumping any python package's version. Anyway, if the community wants to stop bumping major versions in case of dropping python version support, then i'm probably OK with that. Cheers, Előd ________________________________________ From: Jeremy Stanley Sent: Monday, September 23, 2024 15:22 To: openstack-discuss@lists.openstack.org Subject: Re: Stop bumping major versions when dropping EOL Python versions On 2024-09-23 12:25:09 +0100 (+0100), Stephen Finucane wrote: [...]
I'd be in favour of getting rid of this particular constraint, and instead focusing on API changes when deciding whether to bump the major version. Is this a reasonable suggestion, and if so what would we need to do to tweak our policy to allow it?
It makes sense to me. Dropping Python 2.x support was a more significant event, but these days removing support for minor Python versions after the corresponding CPython interpreter reaches EOL upstream is fairly unremarkable. We don't perform major version increments just for raising the minimum required versions of any other dependencies, after all. -- Jeremy Stanley