-<pre><code><repository location="http://www.simantics.org/download/release/x.y.z[.w]/sdk"/>\r
-<repository location="http://www.simantics.org/download/release/x.y.z[.w]/external-components/maven"/>\r
-<repository location="http://www.simantics.org/download/release/x.y.z[.w]/external-components/manual"/>\r
+<pre><code>location "http://www.simantics.org/download/release/x.y.z[.w]/maven" {\r
+location "http://www.simantics.org/download/release/x.y.z[.w]/manual" {\r
+include "http://www.simantics.org/download/release/x.y.z[.w]/org.simantics.sdk.build.targetdefinition.tpd"\r
+location "http://www.simantics.org/download/release/x.y.z[.w]/sdk" {\r
+</code></pre>\r
+</li>\r
+<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%2Fplatform.git;a=commit;h=5271b0faa98303225d00e6cd838d3fc52488545c">gitweb</a> or <a href="https://www.simantics.org:8088/r/#/c/1361/">review 1361</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