+<li>\r
+<p>Edit version number of <code>org.simantics.sdk</code> feature in <code>features/org.simantics.sdk.feature/feature.xml</code> to <code>x.y.z[.w]</code>.</p>\r
+<pre><code><feature\r
+ id="org.simantics.sdk"\r
+ label="Simantics SDK"\r
+ version="x.y.z"\r
+ provider-name="VTT Technical Research Centre of Finland">\r
+</code></pre>\r
+<p>An example of these changes can be seen in <a href="https://www.simantics.org:8088/r/gitweb?p=simantics/platform.git;a=commit;h=bab5c9bd68277c76dc5c20bc7a60a9896cbd1540">gitweb</a>.</p>\r
+</li>\r
+<li>\r
+<p>Ensure that Redmine has a release engineering issue for the branched release, such as <a href="https://www.simantics.org/redmine/issues/7263">Simantics 1.30.0 release engineering</a>. Make a copy of the previous release issue to create the new one. Include link to original issue while copying.</p>\r
+</li>\r
+<li>\r
+<p>Commit the changes made</p>\r
+<pre><code> git commit -a\r
+</code></pre>\r
+<p>with the commit message</p>\r
+<pre><code> Configured release/x.y.z[.w] branch for SDK builds.\r
+\r
+ refs #xxxx\r
+</code></pre>\r
+<p>where <code>#xxxx</code> is the number of the x.y.z[.w] release engineering issue and push them to remote</p>\r
+<pre><code> git push origin release/x.y.z[.w]\r
+</code></pre>\r
+</li>\r
+<li>\r
+<p>If you are branching from <code>master</code>, bump the revision of master right now to start the next release cycle in master.\r
+An example of these changes can be seen in <a href="https://www.simantics.org:8088/r/gitweb?p=simantics/platform.git;a=commitdiff;h=ae93c9930c6345c32219e6845b9e72e9d9d2d28c">gitweb</a>.</p>\r
+<p>Commit the changes with the following commit message</p>\r
+<pre><code>Bumped master target and org.simantics.sdk feature versions to x.y.z[.w].\r
+refs #yyyy\r
+</code></pre>\r
+<p>where <code>#yyyy</code> is the number of the next release's release engineering issue.</p>\r
+</li>\r