-
Notifications
You must be signed in to change notification settings - Fork 327
Release Information
As of the 0.2 release candidates, the project has gone through structural changes to align to standard OSS methodologies. Please review the following information which outlines some of this.
The project expects that branching will be named in standard ways. Please submit Pull Requests with branch names that match the following two types: feature/branch_name, or bugfix/branch_name.
The project is leveraging standard semantic versioning. For example, 0.1.2-rc3+4+dirty as reported through rexray version would mean the following.
| Type | Description |
|---|---|
| 0 | Major |
| 1 | Minor |
| 2 | Patch |
| rc3 | Release candidate 3 |
| 4 | Commits after last tagged release |
| dirty | Whether binary is built with uncommitted code |
The project is leveraging Travis-CI for testing each build as it is checked in and distribute artifacts to proper locations.
Artifacts are available in two main locations and installed via numerous methods. You can find them at the releases page at Github, in addition to Bintray.