update HOWTORELEASE.rst (#126)

* elaborate on releasing steps

* add testenv:release to tox.ini

* remove unnecessary command

* remove virtual env creation

* remove .vscode and add it to .gitignore

* remove testenv:release from tox.ini

Author: northernSage

.gitignore

@@ -3,7 +3,7 @@
 *.egg-info
 build
 sdist
-
+.vscode
 __pycache__/
 
 # virtualenv

HOWTORELEASE.rst

@@ -1,7 +1,29 @@
-Here are the steps on how to make a new release.
+=======================
+Releasing pytest-flask
+=======================
 
-1. Create a ``release-VERSION`` branch from ``upstream/master``.
-2. Update ``docs/changelog.rst``.
-3. Push a branch with the changes.
-4. Once all builds pass, push a tag to ``upstream``.
-5. Merge the PR.
+This document describes the steps to make a new ``pytest-flask`` release.
+
+Version
+-------
+
+``master`` should always be green and a potential release candidate. ``pytest-flask`` follows
+semantic versioning, so given that the current version is ``X.Y.Z``, to find the next version number
+one needs to look at the ``docs/changelog.rst`` file.
+
+Steps
+-----
+
+#. Create a new branch named ``release-X.Y.Z`` from the latest ``master``.
+
+#. After making the necessary changes, commit and push the branch for review.
+
+#. Once PR is **green** and **approved**, create and push a tag::
+
+    $ export VERSION=X.Y.Z
+    $ git tag $VERSION release-$VERSION
+    $ git push git@github.com:pytest-dev/pytest-flask.git $VERSION
+
+    That will build the package and publish it on ``PyPI`` automatically.
+
+#. Merge ``release-X.Y.Z`` branch into master.