Choose project versioning scheme

[brylie]

Choose a scheme for project versions. Include alpha and beta releases in scheme.

Definition of done

• Determine whether semantic versioning is suitable for this project.
• Determine the version for the pre-release.
• Choose how to indicate alpha, beta and release candidate in the release tag.
• If it is, make a semantically versioned pre-release.
• Determine the difference between pre-releases and full releases in terms of branching.

[bajiat]

Semantic versioning specification

[brylie]

Additional resources

Meteor.js specific

• Meteor docs - writing packages - "Meteor packages uses extended semver".
• Meteor docs - package.js - demonstrates semantic versioning in Meteor.js packages
• Meteor packaging system: understanding versioning - describes using semver for meteor projects/packages
• Meteor Cookbook: semver convention

Node.js specific

• semantic versioning and npm
• NPM packages often use semver

General guidelines

• Semantic Versioning: Why You Should Be Using it

[bajiat]

• Determine whether semantic versioning is suitable for this project.
  • Semantic versioning is the standard way.
  • To be used as in the semantic versioning standard Major.Minor.Patch without leading zeros
  • 1.0.0-alpha – alpha and beta spelled out for clarity
  • Rc should also be used: 1.0.0-rc1
• First release should be 0.1.0
• For any milestone, we’ll need to make a stable release
• At least one pre-release for every sprint
  • To be made on Mondays prior to new sprint planning
  • Rotating release task responsibility, working with project owner
• Nightly builds made from development branch and not tight to official releases
• 0.1.0 to be made from master, requires pulling from the dev branch
• Each time we make a release, we need to decide whether it’s a minor version or a patch

[bajiat]

Made the initial alpha release!

[bajiat]

Task almost complete

• "Determine the difference between pre-releases and full releases in terms of branching" > to be defined after we get some more understanding.
• Need to document the versioning scheme in GitHub.

[bajiat]

Versioning scheme documented in docs/developers/release-versioning.md