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

Hope to have an ordinary version number instead of '20140215' #203

Closed
spacewander opened this issue Oct 6, 2014 · 8 comments
Closed

Hope to have an ordinary version number instead of '20140215' #203

spacewander opened this issue Oct 6, 2014 · 8 comments
Assignees
Milestone

Comments

@spacewander
Copy link
Contributor

I suggest to use an ordinary version number like 'x.y.z' instead of using '20140215'.
Because:

  1. using 'x.y.z' is more clear than '20140215', especially when we talk about the binary distribution.
  2. since the current version of zeal is very different from one in Feb 15th, 2014.
  3. using 'x.y.z', we can make the change log more clear, and more reasonable.
@PythonNut
Copy link

+1 for a semantic versioning scheme.

@henrikp
Copy link
Contributor

henrikp commented Dec 11, 2014

I would like to see this as well.

@jkozera
Copy link
Member

jkozera commented Jan 6, 2015

@spacewander not resolved - reopening

@jkozera jkozera reopened this Jan 6, 2015
@spacewander
Copy link
Contributor Author

@jkozera I am sorry... I should close it after asking others' advice. I am very sorry about my impertinence.

@jkozera
Copy link
Member

jkozera commented Jan 6, 2015

@spacewander don't worry, we all make mistakes, and it's good to close outdated issues. :) If you want do discuss anything, or perhaps just chat in general, please come to #zealdocs @ freenode IRC, we have some discussion going on there.

@trollixx
Copy link
Member

Fixed with 0.1.0 release.

@spacewander
Copy link
Contributor Author

👍

@lock
Copy link

lock bot commented Sep 16, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for a related request.

@lock lock bot locked and limited conversation to collaborators Sep 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

5 participants