-
Notifications
You must be signed in to change notification settings - Fork 1
Versioning
Robbie Averill edited this page Jan 5, 2017
·
1 revision
SilverLeague modules will always follow semantic versioning as strictly as possible, e.g. major.minor.patch. This means that:
- Major version bumps will break the public API, and/or backwards compatibility
- Minor version bumps will add functionality in a backwards compatible manner, and;
- Patch version bumps will fix broken functionality in a backwards compatible manner
Modules will be released as 1.0.0 once they move from the "in development" proposal phase to the "active support" proposal phase. Until then they may or may not have released tagged, but if they are done they will be released as ^0.1.
All SilverLeague modules will define a branch alias for their master branch to be aliased as the next version to be released.