Version scheme about pudding-bot HOT 2 CLOSED

The best way to go about this for the foreseeable future is a SemVer release cycle using the Git SHA as the final identifier, in place of "Alpha" or "Beta". Once we hit 1.0.0, we can further amplify this with "RC" tags.

For now, all non-tagged versions should use the scheme
Major.Minor.Patch-SHA, whereas tagged versions would simply be Major.Minor.Patch.

After version 1.0.0, a version scheme could look like this:

• 1.0.1-37c2a4f
• 1.1.0-RC1
• 1.1.0

Where the latter two are tagged releases.

All changes should be documented in the CHANGELOG, regardless of whether the release is tagged or not.

from pudding-bot.

TODO:

• Clean up previous commits (some commit messages are non-canonical/use the wrong tense).
• Run git rev-parse --short <COMMIT>/HEAD (where COMMIT/HEAD is either the HEAD or a SHA) on existing commits.
• Add CHANGELOG with existing versions (all non-tagged, so far. 0.0.6 will be the first tagged version).
• Store current version as a string in version.py.

The initial CHANGELOG should go into a separate commit rather than be amended to an existing one, to avoid SHA Confusion.

from pudding-bot.