Consider post-release version tags

[mrnicegyu11]

Is there an existing issue for this?

• I have searched the existing issues

User Story

Follow-up solution from ITISFoundation/osparc-ops-environments#866 , specifically for addressing this:

“still a problem to have the repository with some data, and portainer having different values”

Definition of Done

No response

[pcrespov]

Version specifiers

• 1.0.dev1 < 1.0a1 < 1.0b1 < 1.0rc1 < 1.0 < 1.0.post1

1. 1.0.dev1: A development release leading up to 1.0. This is considered earlier than any alpha, beta, release candidate, or final release.
2. 1.0a1: The first alpha pre-release, indicating an early, unstable version.
3. 1.0b1: The first beta pre-release, more stable than alpha but still not final.
4. 1.0rc1: The first release candidate, which is almost final but might still have minor issues.
5. 1.0: The final release, the official and stable version.
6. 1.0.post1: The first post-release, indicating a minor update or fix after the final 1.0 release.

References

• Python Packaging User Guide:
  • Version specifiers in python-packaging
• packaging library
  • https://packaging.pypa.io/en/stable/
• Semantic versioning:
  • https://semver.org/