Skip to content

New Odin Versioning System for Pre Version 1.0 #887

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

Closed
gingerBill opened this issue Mar 31, 2021 · 6 comments · Fixed by #914
Closed

New Odin Versioning System for Pre Version 1.0 #887

gingerBill opened this issue Mar 31, 2021 · 6 comments · Fixed by #914

Comments

@gingerBill
Copy link
Member

The current versioning system in Odin has not been working very well and does not map very well to the development of Odin, its official compiler, and the core library. Once v1.0 has been reached, an actual semantic versioning convention will be used.

As a proposal, I am suggesting we change the naming convention to be monthly based, which each month there being a new release regardless of how big or small the changes have been.

General ideas for the naming convention:

dev-2021.04
alpha-2021.04
@gingerBill
Copy link
Member Author

This versioning system is to be automatically handled by the monthly build system rather than by hand.

In the very unlikely case that there are no changes the has happened in that month, then a build should not be produced for that month.

The monthly build system should build a release near the beginning of that month (compared to nearer the end of the month) so that users know that they are on the latest one.

@goolic
Copy link

goolic commented Apr 1, 2021

I would propose dev-2021.04.build01, sometimes you will ship a mistake and issue several new builds in a row to try and resolve it, this scheme makes that super clear.

@gingerBill
Copy link
Member Author

If a multiple build is required, a letter will be appended (like housing numbers). If people want the most recent build, the use can use a nightly build.

@goolic
Copy link

goolic commented Apr 1, 2021 via email

@gingerBill
Copy link
Member Author

This was not an April Fool's Joke but an absolutely serious proposal. We are going to transition from "v0.13.1" style release numbers to using monthly releases before version 1.0 is released.

@Platin21
Copy link
Contributor

Platin21 commented Apr 5, 2021

I think the initial proposal of <Modifier>-<YYYY>-<0M> is pretty good. Not sure if the pace is now considered to be faster but if it's a running number for the month might not be too bad?

I did also like to have a part of the commit hash inside the version so it's easier to refer to it..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants