Skip to content

Switch to proper semantic versioning #1303

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.

Sign up for GitHub

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

Jump to bottom
Closed
nhooyr opened this issue Jan 28, 2020 · 2 comments · Fixed by #1338
Closed

Switch to proper semantic versioning #1303

nhooyr opened this issue Jan 28, 2020 · 2 comments · Fixed by #1338
Assignees
@kylecarbs @sr229 @code-asher
Labels
enhancement Some improvement that isn't a feature

Comments

@nhooyr
Copy link
Contributor

nhooyr commented Jan 28, 2020 •
edited
Loading

We were discussing and the current version numbers are confusing as the build number doesn't communicate much.

cc @kylecarbs

Major would be big changes, minor for new features and patch for bug fixes.
@nhooyr nhooyr added the enhancement Some improvement that isn't a feature label Jan 28, 2020
@nhooyr nhooyr changed the title Switch to proper calendar versioning Switch to proper semantic versioning Jan 28, 2020
@sr229
Copy link
Contributor

sr229 commented Jan 28, 2020

I think we should also ditch the -vsc-x.y.z since it'll make it hard for automation software to cope up with latest releases. I think we can do that right now by editing the build script.

@sr229 sr229 self-assigned this Jan 28, 2020
@sr229 sr229 mentioned this issue Jan 28, 2020
Closed
@kylecarbs
Copy link
Member

I agree the build number doesn't say much

@code-asher code-asher mentioned this issue Feb 24, 2020
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kylecarbs kylecarbs

@sr229 sr229

@code-asher code-asher

Labels
enhancement Some improvement that isn't a feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Restructure coder/code-server
4 participants
@kylecarbs @nhooyr @sr229 @code-asher