-
Notifications
You must be signed in to change notification settings - Fork 0
Versioning Practices
dchandekstark edited this page Nov 6, 2014
·
4 revisions
Our basic practice should follow the versioning patterns of RubyGems:
- Major: x.0.0
- Minor: 0.x.0
- Patch: 0.0.x
Version 1.0.0 shall be considered the initial release for production use.
Subsequent to a numbered x.x.x release, .post should be appended to the version number in the develop branch (see Branching and Tagging).
In certain circumstances it may be useful to create a "release candidate" release. These releases should have a version suffix .rcX, where X is an integer starting with 1 for the first release candidate version.
In this context, "dependencies" means gems explicitly required in the project Gemfile.
- Upgrade to existing dependencies: Patch-level release
- Addition of new dependencies: Minor release