You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thank you for your continued work on this project — it’s greatly appreciated.
I would like to kindly suggest the adoption of Semantic Versioning for both Git tags and Docker image tags. Implementing a consistent versioning strategy would significantly improve clarity, traceability, and interoperability for users and integrators of the project.
Proposed Improvements
• Git Tags: Use semantic versioning format (vMAJOR.MINOR.PATCH, e.g., v1.2.3) for Git releases to clearly communicate the nature of changes.
• Docker Images: Tag Docker images with corresponding SemVer versions (e.g., yourimage:1.2.3) and, optionally, maintain supporting tags such as latest, 1, or 1.2 for convenience.
• Documentation: Include a brief note in the README or contributing documentation about the versioning policy.
Benefits
• Improved integration in CI/CD workflows
• Easier version tracking and rollback capabilities
• Clear communication of breaking changes vs. minor improvements or patches
• Compatibility with common versioning expectations across the software ecosystem
Thank you again for your time and consideration!
The text was updated successfully, but these errors were encountered:
Dear Team,
First, thank you for your continued work on this project — it’s greatly appreciated.
I would like to kindly suggest the adoption of Semantic Versioning for both Git tags and Docker image tags. Implementing a consistent versioning strategy would significantly improve clarity, traceability, and interoperability for users and integrators of the project.
Proposed Improvements
• Git Tags: Use semantic versioning format (vMAJOR.MINOR.PATCH, e.g., v1.2.3) for Git releases to clearly communicate the nature of changes.
• Docker Images: Tag Docker images with corresponding SemVer versions (e.g., yourimage:1.2.3) and, optionally, maintain supporting tags such as latest, 1, or 1.2 for convenience.
• Documentation: Include a brief note in the README or contributing documentation about the versioning policy.
Benefits
• Improved integration in CI/CD workflows
• Easier version tracking and rollback capabilities
• Clear communication of breaking changes vs. minor improvements or patches
• Compatibility with common versioning expectations across the software ecosystem
Thank you again for your time and consideration!
The text was updated successfully, but these errors were encountered: