Versioning strategy

[Jaci-Arch]

Discussion Prompt:

As a team, we are currently struggling with establishing a consistent and effective versioning strategy for our software projects. We have several questions and concerns that we would like to discuss:

• Which versioning scheme should we use? We are considering Semantic Versioning (SemVer) but are also open to other options like Date-based or Feature-based versioning.
• How should we handle pre-release versions? Should we include a "beta" or "rc" label in the version number, or should we use a separate branch for pre-releases?
• What should we do with outdated versions? How long should we support old versions, and how should we handle security vulnerabilities in older releases?
• How should we document our versioning strategy? What information should we include in our release notes, and how should we communicate changes to our users?

Your Input:

We would love to hear your thoughts and experiences with versioning strategies. Please share your insights on the following:

• Your preferred versioning scheme and why.
• Best practices for handling pre-release versions.
• Strategies for managing outdated versions and security vulnerabilities.
• Tips for documenting and communicating your versioning strategy effectively.

By participating in this discussion, we hope to establish a clear and consistent versioning strategy that will help us improve our software development process and provide better support for our users.