doc/howto-publish-a-release.md
Before you can do anything else, you need to decide what should be included in the new version.
Bugfix releases bump the third number of the version, e.g. 1.9.0 -> 1.9.1.
They may include bugfix commits that you git cherry-picked from the master
branch into the stable branch, or you can just do a fast-forward merge of
master into stable, if there were only bugfix commits since the last major
version. You can also add minor new features that are very likely not causing
any bugs. However, there should be absolutely no backward-incompatible
changes, like:
New settings are okay, just make sure a sane default value is defined.
Major releases bump the second number of the version, e.g. 1.9.2 -> 1.10.0 and are necessary if you introduce any breaking changes, like the ones mentioned in the list above.
make test./ranger.py [--clean]ranger/ext/rifle.pymake installREADME__version__ and __release__ in ranger/__init__.py__version__ in ranger/ext/rifle.pymake mangit tag -as vX.Y.Z, using the same
commit message as annotation.tar.gz with make snapshotmakemake installranger-stable.tar.gzranger-X.Y.Z.tar.gzgpg --local-user 0x00FB5CDF --sign --detach-sign <file>make manhtml in ranger's repositorydoc/ranger.1.html to the pages repositoryREADME.md in the pages repositorygit clean --force -d -xpython setup.py sdistgpg --local-user 0x00000000 --detach-sign --armor dist/*twine upload dist/*__release__ in ranger/__init__.py back to False