-
Notifications
You must be signed in to change notification settings - Fork 134
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 inconsistency? #309
Comments
I know :-) On 3 October 2012 18:14, Marco Bernasocchi notifications@github.com wrote:
|
In my opinion we should set version in two places: #1. safe/init.py, the following way, this is the python-safe version: version = (0, 6, 0, 'alpha', 0) #2. metadata.txt (the qgis-safe or inasafe version): version=0.6.0 Longer version of the response: Furthermore, and answering the 'bleeding edge' version question, here is We should call the bleeding edge: 0.6-dev{dateandtime} this is done automatically when the version string is set as:
This was working before this commit [1](that I did not notice until For the record, below is how python itself handles versioning, and the
I should also say that versioning is really important to me, as the "python-safe>=0.5" Ariel. [1] On Wed, Oct 3, 2012 at 7:57 AM, Ole Nielsen notifications@github.comwrote:
|
https://github.com/AIFDR/inasafe/blob/7ae27f8b41668724beec5043c9bc205c150914ff/__init__.py
is there a reason why metadata.txt and version have 0.6.0 but
version():
"""Version of the plugin."""
return 'Version 0.5.0'
The text was updated successfully, but these errors were encountered: