-
Notifications
You must be signed in to change notification settings - Fork 77
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
DOC: semver.rst: Examples (TODO) #14
DOC: semver.rst: Examples (TODO) #14
Conversation
|
||
# Git short-sha Development (*) versions | ||
1.0.0.a1.g95a9beb | ||
1.0.0.c999.g95a9beb (TODO: ?) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way to include a git short-sha without a Development version?
1.0.0.c999.g95a9beb
1.0.0..g95a9beb ?
|
||
# Git short-sha and ISO8601 build metadata (* TODO: ?) | ||
1.0.0.a1.g95a9beb+2013-03-13T14:47:00-0000 | ||
1.0.0.a1.g95a9beb+2013-03-13T14:47:00+Z |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a guideline for this? The build metadata is arbitrary, but, as always, ISO8601 doesn't sort unless the timezone is always the same (which isn't the case in regions with daylight savings time), so the only sortable ISO8601 options are:
-0000
+0000
-Z
+Z
Alternatively, Unix time (seconds since the epoch) is sortable.
I suppose the #headings here could be normalized to the wording from PEP440:
|
It may also be worth mentioning that
|
Thank you for contributing to openstack-dev/pbr! openstack-dev/pbr uses Gerrit for code review. If you have never contributed to OpenStack before make sure you have read the Otherwise please visit |
https://bugs.launchpad.net/pbr/+bug/1629199