Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change versioning convention to calendar based #23

Open
Tracked by #24
maxpowis opened this issue Aug 4, 2023 · 2 comments
Open
Tracked by #24

Change versioning convention to calendar based #23

maxpowis opened this issue Aug 4, 2023 · 2 comments
Assignees
Labels
devops Continuous integration/deployment

Comments

@maxpowis
Copy link
Owner

maxpowis commented Aug 4, 2023

Release mgmt standard currently uses semver.org as a reference for release/document versioning.
Idea is to switch to a certain flavor of calver.org to better reflect the period to which the generated cv is valid.

@maxpowis maxpowis added the devops Continuous integration/deployment label Aug 4, 2023
@maxpowis maxpowis self-assigned this Aug 4, 2023
@maxpowis maxpowis changed the title Change versioning convention to calver Change versioning convention to calendar based Aug 4, 2023
@maxpowis
Copy link
Owner Author

maxpowis commented Aug 4, 2023

I am considering the format YYYY.0M or YYYY.0M-MICRO based on calver.org

@maxpowis
Copy link
Owner Author

maxpowis commented Aug 4, 2023

Based on https://nehckl0.medium.com/semver-and-calver-2-popular-software-versioning-schemes-96be80efe36 new idea is to have

YYYY.0M.BUILD-STATUS

Image

@maxpowis maxpowis moved this from Todo to In Progress in @maxpowis's professional cv Aug 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops Continuous integration/deployment
Projects
Status: In Progress
Development

No branches or pull requests

1 participant