Steps to release¶
Create a branch¶
Name the branch following the guidelines of semantic versioning http://semver.org/:
MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backwards-compatible manner, and
- PATCH version when you make backwards-compatible bug fixes.
$ git checkout master $ git checkout -b release/0.2.2 $ git push --set-upstream origin release/0.2.2
Draft the release¶
This step should be done at the very beginning of planning. If you already did it, skip it now.
At code -> releases draft a new release
- tag version : v0.2.2
- release title : v0.2.2
Create the milestone¶
At the issues section , create a milestone. Name it like the tag version: 0.2.2. There must be a way to link it to the tag , I just don’t know how.
Assign issues to the milestone
Update the release number¶
Modify lib/Ravada.pm around line 5:
our $VERSION = '0.2.5';
Modify the Changelog¶
Check the last issues closed for this milestone and add them to the Changelog file:
$ git checkout release/0.2.2 $ gvim Changelog.md $ git commit -a
$ git push
Close the release¶
Make sure the target is the same as the branch, not the master. Close the release at:
- Close the Milestone
- Publish the Release
Create the debian package.
$ fakeroot ./deb/debianize.pl $ lintian ravada_0.8.1_all.deb
Upload the file to our repo and change the number at:
http://ravada.readthedocs.io/en/latest/docs/INSTALL.html $ git checkout gh-pages $ gvim docs/docs/INSTALL.md $ gvim docs/docs/res/ravada_installer.sh $ gvim index.html $ git commit -a $ git push
In a test machine, upgrade ravada following:
In a fresh machine, install it following the whole process: