- changed status to open
Version number scheme
Issue #104
closed
I would like to use sources distribution instead of git to deploy on the new server and I propose that we use actual version number instead of aXX.
In particular it would be nice to be able to identify which new version introduce a db change, so I suggest using MAJOR.MINOR.PATCH where MAJOR would be 2 for now (but if we ever add an API, we can increment the MAJOR version when the API changes), MINOR is incremented when the database schema changes and PATCH for bug-fixes and changes that don't require changing the database.
Comments (3)
-
reporter -
http://semver.org/ FTW
-
reporter - changed status to closed
Implemented and documented in pull request #17
- Log in to comment