Version using 5.0.0a0

[Jibola]

Reverting to 5.0a0 to get the automated versioning to release 5.0a0

[aclark4life]

I don't know if it's relevant here, but I'd expect 5.0.0a0

[timgraham]

Django has never used ".0" in version numbers, even "5.0.0" (final). I don't see a need for a micro version number in pre-release version numbers, especially because we're never going to have something like "5.0.1a1".

One thing I wasn't sure about when you mentioned your intention to release "alpha 0" is whether that's a thing. I've never seen a version like that on PyPI.

There's a mention of "a0" at https://peps.python.org/pep-0440/#implicit-pre-release-number.

It's not relevant for this situation, but Django's version utility treats "alpha 0" as a development version: https://github.com/django/django/blob/a9c79b462923ce366101db1b5a3fff3d1dad870c/django/utils/version.py#L37-L40

All that to say, if "alpha 0" isn't working with the automated tooling, I wouldn't be completely surprised.

[aclark4life]

LGTM

[Jibola]

Based on the feedback here and checking what we do over in mongo-python-driver. I think the best marriage of the two ecosystems would be to switch to the 5.0.0a0 nomenclature.

Here's a pymongo 4.8.0b0 release that works within the semantic versioning.

[aclark4life]

@timgraham There's also this: https://packaging.python.org/en/latest/discussions/versioning/#choosing-a-versioning-scheme

[aclark4life]

Even better!