Commit 7f06186e authored by Francesc Guasch's avatar Francesc Guasch
Browse files

Removed steps to release docs, it is private now

parent 2e79b64b
Steps to release
Create a branch
Name the branch following the guidelines of semantic versioning
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.
Create issues
Assign issues to the milestone
Close the milestone
Check the milestone has no open issues and close it.
Update the authors
$ git checkout 0.2.2
$ cd templates/bootstrap/
$ ./
It will create a file *authors.html.ep*, review it and commit it.
$ git commit authors.html.ep
$ cd ../..
Update the release number
Modify *lib/* 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
$ git commit -a
Push changes
$ 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
Release binary
Create the *debian* package.
$ fakeroot ./deb/
$ lintian ravada_0.8.1_all.deb
Upload the file to our repo and change the number at:
$ git checkout gh-pages
$ gvim docs/docs/
$ gvim docs/docs/res/
$ gvim index.html
$ git commit -a
$ git push
Install it
In a test machine, upgrade ravada following:
In a fresh machine, install it following the whole process:
- Tweet it
- Mail it in google group
- Change the release in branch master
......@@ -152,7 +152,6 @@ Do you feel like giving us a hand? Here you have all the information you need as
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment