Since Open vStorage is running in production at customers we need to carefully plan our releases as a small glitch might cause a disaster. For storage software there is a golden rule
If it ain’t broken, don’t fix it!
With the release of Fargo RC1 we are entering a new cycle of intermediate releases and bugfixes. Once Fargo is GA we will push out a new update at regular intervals. Before installing an update customers like to know what is exactly fixed in a certain update. That is why for each release, even an intermediate release, the release notes are documented. Let’s take as an example the Fargo Release Candidate 1. This release consists out of following packages:
- openvstorage-backend-core: 1.7.4-fargo.1-1
- volumedriver-no-dedup-base: 6.3.1-0
- alba: 1.0.0
- openvstorage-sdm: 1.6.4-fargo.1-1
- openvstorage-webapps: 2.7.4-fargo.1-1
- volumedriver-no-dedup-server: 6.3.1-0
- openvstorage-backend-webapps: 1.7.4-fargo.1-1
- openvstorage-core: 2.7.4-fargo.1-1
- openvstorage: 2.7.4-fargo.1-1
- openvstorage-cinder-plugin: 1.2.2-fargo.1-1
- openvstorage-backend: 1.7.4-fargo.1-1
- arakoon: 1.9.15
The content of each package e.g. the webapps package can be found on the appropriate repository (or you can click the link in the release notes). The release notes of the package contain a summary of all fixed issues in that exact package. In case you want to be kept up to date of new releases, add the the release page as RSS feed (https://github.com/openvstorage/home/releases.atom) to your favourite RSS Feed reader. If you prefer to be kept up to date by email, you can use Sibbell, Blogtrottr or a similar service.