We'll use release* eventually in CI so reflect that in checklist

paritytech · Jun 14, 2021 · 0a2c243 · 0a2c243
1 parent 6d3bd8c
commit 0a2c243
Showing 1 changed file with 4 additions and 3 deletions.
diff --git a/RELEASING.md b/RELEASING.md
@@ -4,9 +4,10 @@ These steps assume that you've checked out the Soketto repository and are in the
 
 1. Ensure that everything you'd like to see released is on the `develop` branch.
 
-2. Create a release branch off `develop`, for example `jsdw-release-v0.6.0`. You'll want to decide how 
-   far the version needs to be bumped based on the changes to date. If unsure what to bump the version 
-   to (eg is it a major, minor or patch release), check with the Parity Tools team.
+2. Create a release branch off `develop`, for example `release-v0.6.0`. The branch name should start with `release`
+   in order that we can target commits with CI. You'll want to decide how far the version needs to be bumped 
+   based on the changes to date. If unsure what to bump the version to (eg is it a major, minor or patch 
+   release), check with the Parity Tools team.
 
 2. Make sure that the tests pass.