-
Notifications
You must be signed in to change notification settings - Fork 11
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
Version Fiasco! #36
Comments
I've started working on this, based on the plan @slifty originally proposed in this thread. So far I have done the following:
We still need to archive these branches so they don't distract us (typically I do that by putting them in the
Once the above is done I'll see if anything remains in this issue, but I think that will address most of it. Possibly we should either update the version number in |
As per issue #36, this number's maintenance may be automated later. For now, the number can at least be up to date.
Okay, the
Closing this issue. |
Our version numbers are kind of out of control. The repo has the following versions listed depending on where you look:
0.3.0 (branch version)
1.0.0 (version listed in application.properties)
0.0.1 (this may just be local to me...)
v3 (version in the URL)
Version 2 (version in the repo description)
Proposed resolutions:
The text was updated successfully, but these errors were encountered: