Upgrade the version to 2.7.0-dev0 following 2.6.0 release

1 files changed, 11 insertions, 19 deletions

diff --git a/doc/release.md b/doc/release.md
index c37be3dc..57e05776 100644
--- a/doc/release.md
+++ b/doc/release.md
@@ -7,7 +7,15 @@ So, you want to release the `X.Y.Z` version of astroid ?
 1. Check if the dependencies of the package are correct
 2. Install the release dependencies `pip3 install pre-commit tbump`
 3. Bump the version and release by using `tbump X.Y.Z --no-push`.
-4. Check the result.
+4. Check the result. If it was a minor release add a `X.Y+1.0` title following the
+   template:
+
+```text
+What's New in astroid x.y.z?
+============================
+Release Date: TBA
+```
+
 5. Push the tag.
 6. Release the version on GitHub with the same name as the tag and copy and paste the
    appropriate changelog in the description. This trigger the pypi release.
@@ -19,7 +27,8 @@ So, you want to release the `X.Y.Z` version of astroid ?
 Move back to a dev version with `tbump`:
 
 ```bash
-tbump X.Y.Z-dev0 --no-tag --no-push # You can interrupt during copyrite
+tbump X.Y+1.Z-dev0 --no-tag --no-push # You can interrupt during copyrite
+git commit -am "Upgrade the version to x.y+1.z-dev0 following x.y.z release"
 ```
 
 Check the result and then upgrade the master branch
@@ -28,20 +37,3 @@ Check the result and then upgrade the master branch
 
 We move issue that were not done in the next milestone and block release only if it's an
 issue labelled as blocker.
-
-### Files to update after releases
-
-#### Changelog
-
-If it was a minor release add a `X.Y+1.0` title following the template:
-
-```text
-What's New in astroid x.y.z?
-============================
-Release Date: TBA
-```
-
-#### Whatsnew
-
-If it was a minor release, create a new `What's new in Astroid X.Y+1` document. Take a
-look at the examples from `doc/whatsnew`.