<li>Simantics R - <a href="https://www.simantics.org:8088/r/gitweb?p=simantics/r.git;a=summary">simantics/r.git</a></li>\r
<li>FMIL - <a href="https://www.simantics.org:8088/r/gitweb?p=simantics/fmil.git;a=summary">simantics/fmil.git</a></li>\r
<li>FMI Studio - <a href="https://www.simantics.org:8088/r/gitweb?p=members/fmi.git;a=summary">members/fmi.git</a></li>\r
-<li>Simupedia - <a href="https://www.simantics.org/svn/members/simupedia">Members SVN</a></li>\r
+<li>Simupedia - <a href="https://www.simantics.org:8088/r/gitweb?p=members/simupedia.git;a=summary">members/simupedia.git</a></li>\r
</ul>\r
<p>For simplicity, each of these components are versioned accoring to platform versioning, i.e. for Platform SDK 1.26.0 there will be Simantics Desktop 1.26.0, Sysdyn 1.26.0, and so on.</p>\r
<hr />\r
<li><code>simantics.target</code></li>\r
<li><code>org.simantics.sdk.build.targetdefinition.target</code></li>\r
</ul>\r
-<p>At the beginning of simantics.target file, increment <code>sequenceNumber</code> by 1</p>\r
+<p>At the beginning of simantics.target file, increment <code>sequenceNumber</code> by 1 and replace\r
+the version numbers in target name and <code>org.simantics.sdk.feature.group</code> and\r
+<code>org.simantics.sdk.source.feature.group</code> with <code>x.y.z[.w]</code>:</p>\r
<pre><code><?xml version="1.0" encoding="UTF-8" standalone="no"?>\r
<?pde version="3.8"?>\r
<target name="Simantics x.y.z[.w]" sequenceNumber="11">\r
+<unit id="org.simantics.sdk.feature.group" version="x.y.z[.w]"/>\r
+<unit id="org.simantics.sdk.source.feature.group" version="x.y.z[.w]"/>\r
</code></pre>\r
<p>Next, replace the following rows in both mentioned files:</p>\r
<pre><code><repository location="http://www.simantics.org/download/master/sdk"/>\r
<repository location="http://www.simantics.org/download/release/x.y.z[.w]/external-components/manual"/>\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/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
</ol>\r
<h3>Initialize release branch distribution web site</h3>\r
<ul>\r
<h2>Tag release/* branches</h2>\r
<p>When the release branches are ready for the release, tag them with the tag <code>vx.y.z[.w]</code>:</p>\r
<pre><code>git clone ssh://<user>@www.simantics.org:29418/simantics/platform.git\r
-cd platform \r
+cd platform\r
git checkout release/x.y.z[.w]\r
-git tag vx.y.z[.w] -m "Simantics x.y.z[.w] release"\r
+git tag vx.y.z[.w] -m "Simantics x.y.z[.w] simultaneous release"\r
git push origin --tags\r
\r
git clone ssh://<user>@www.simantics.org:29418/simantics/third-party.git\r
cd third-party\r
git checkout release/x.y.z[.w]\r
-git tag vx.y.z[.w] -m "Simantics x.y.z[.w] release"\r
+git tag vx.y.z[.w] -m "Simantics x.y.z[.w] simultaneous release"\r
git push origin --tags\r
</code></pre>\r
<blockquote>\r
at a later time for some reason, we'll put the documentation up then in a\r
separate Mediawiki installation.</p>\r
<ol>\r
-<li>Dump documentation wiki databases using [dump-wikis.sh](./dump-wikis.sh) script.</li>\r
+<li>Dump documentation wiki databases using <a href="./dump-wikis.sh">dump-wikis.sh</a> script.</li>\r
<li>Put the generated backup x.y.z.tar.gz at /var/backup/simantics-releases/x.y.z/wiki/</li>\r
</ol>\r
<h2>Compile change log entry</h2>\r
</ul>\r
<h2>Disseminate information about the release</h2>\r
<ul>\r
-<li><a href="http://dev.simantics.org">Developer Wiki</a>: Update roadmap at http://dev.simantics.org/index.php/Roadmap</li>\r
-<li><a href="https://www.simantics.org/redmine/">Redmine</a>: Post news on the developer/user-visible changes here.</li>\r
+<li><a href="http://dev.simantics.org">Developer Wiki</a>: Update roadmap at <a href="http://dev.simantics.org/index.php/Roadmap">http://dev.simantics.org/index.php/Roadmap</a></li>\r
+<li><a href="https://www.simantics.org/redmine/">Redmine</a>: Post news on the developer/user-visible changes here</li>\r
<li><a href="https://www.simantics.org">simantics.org</a>: Post news on the release and a link to the redmine post</li>\r
<li><a href="https://www.simantics.org/members/">Members Wiki</a>: Update frame plan to reflect the realized dates and link to Redmine news</li>\r
<li><a href="mailto:simantics-developers@simantics.org">mailto:simantics-developers@simantics.org</a> Send "newsletter" to `simantics-developers@simantics.org:</li>\r
</ul>\r
<p><strong>Newsletter template:</strong></p>\r
<pre><code>Hello everyone,\r
- \r
+\r
Simantics release x.y.z[.w] has been released. Head over to\r
https://www.simantics.org/redmine/news/<news number>\r
for the release news.\r
<hr />\r
<h1>TODO</h1>\r
<ul>\r
+<li>Start using <a href="https://github.com/mbarbero/fr.obeo.releng.targetplatform">https://github.com/mbarbero/fr.obeo.releng.targetplatform</a> to generate <code>.target</code> files. <code>.tpd</code> files allow specifying version ranges instead of specific versions.</li>\r
+</ul>\r
+<ul>\r
<li>Create a parametrized release train pipeline build in Jenkins that creates all artifacts of a simantics release\r
<ul>\r
<li>Desktop, Sysdyn, R, Simupedia, FMIL, FMI Studio</li>\r
</li>\r
</ul>\r
<ul>\r
-<li>\r
-<p>Incorporate tutorial code in the platform repository as a separate folder to allow platform builds to directly ensure that the tutorial code still builds OK</p>\r
-</li>\r
-<li>\r
-<p>Start using https://github.com/mbarbero/fr.obeo.releng.targetplatform to generate <code>.target</code> files. <code>.tpd</code> files allow specifying version ranges instead of specific versions.</p>\r
-</li>\r
+<li>Incorporate tutorial code in the platform repository as a separate folder to allow platform builds to directly ensure that the tutorial code still builds OK</li>\r
</ul>\r
\r
</body>\r