We follow the scheme described here, which can be summarised like this:
master
: only stable, released codedevelop
: latest updates, new features integrated here
Three additional types of branches are used:
release
: to prepare a release. Branches off ofdevelop
, do the final things, merge intomaster
.feature
: Should be prefixed withfeature/
and ideally correspond to an issue id. Branches off ofdevelop
and is integrated intodevelop
fix
: For bug fixes
- Make a new branch for the release (e.g.
release/1.0.0
) - Set all version numbers to the correct version
DESCRIPTION
file for the R packageREADME.md
for badge
- Check that the R package is well:
make check
- Make a source package by running
make build
- If all works well, merge the branch into master, tag it with
v1.0.0
- Create a new release on the github release page
- Copy the following installations instructions in release note (with fixed version numbers)
install_github("quadrama/DramaAnalysis", ref="v2.0.0")
- Add the PDF documentation for the R package to the release page