<li><a href="https://www.simantics.org/redmine/projects/simantics-platform/wiki/ChangeLog">A change log entry</a> is compiled from the issues in this release and made available to the general public separately for the platform and for the open products included in the release train.</li>\r
<li><a href="http://dev.simantics.org/index.php/Roadmap">Roadmap</a> is up-to-date.</li>\r
<li><a href="http://dev.simantics.org/index.php/Tutorials">Tutorials</a> are up-to-date and coherent with the platform.</li>\r
-<li>For all new major/minor releases, Wiki documentation is backed up (cloned). This is not necessary for service releases of old release branches.</li>\r
+<li>For all new major/minor releases, Wiki documentation is backed up (cloned).</li>\r
</ol>\r
+<hr />\r
<h1>Simantics Platform Release Process</h1>\r
<ul>\r
<li>Create <code>release/x.y.z[.w]</code> release stabilisation branch</li>\r
</ul>\r
</li>\r
<li>Tag the release in repository</li>\r
-<li>Tag documentation\r
+<li>Backup documentation wiki databases</li>\r
+<li>Build and publish SDK package with and without sources\r
<ul>\r
-<li><a href="https://www.simantics.org/wiki">https://www.simantics.org/wiki</a> ⇒ <a href="http://www.simantics.org/%3Cversion%3E/wiki">http://www.simantics.org/<version>/wiki</a></li>\r
+<li>Does not really require any work</li>\r
</ul>\r
</li>\r
-<li>Build and publish SDK package with and without sources</li>\r
-<li>Build Simantics open source products and plug-in components which are a part of the release train\r
+<li>Build Simantics open source products and plug-in components which are a part of the release train</li>\r
+<li>Update websites to reflect the new release</li>\r
+</ul>\r
+<hr />\r
+<h1>Released Plug-in Components and Products</h1>\r
+<p>There are both plug-in components and products that are part of the "Simantics release train" that shall be released simultaneously to a major or minor Simantics release.</p>\r
+<p>Plug-in components are installable features that are deployed online as P2 repositories for general availability. Products are deployed as ZIP files and made available online in designated locations on simantics.org.</p>\r
+<p>Products that are part of the release train:</p>\r
<ul>\r
-<li>Simantics Sysdyn</li>\r
-<li>Simantics R</li>\r
-<li>Simupedia</li>\r
-<li>FMI Studio</li>\r
+<li>Simantics Desktop</li>\r
+<li>Simantics System Dynamics Tool - <a href="https://www.simantics.org:8088/r/gitweb?p=simantics/sysdyn.git;a=summary">simantics/sysdyn.git</a></li>\r
</ul>\r
-</li>\r
-<li>Update websites to reflect the new release\r
+<p>Plug-in components that are part of the release train:</p>\r
<ul>\r
-<li><a href="http://dev.simantics.org">dev.simantics.org</a></li>\r
-<li><a href="https://www.simantics.org/end_user_wiki/">www.simantics.org/end_user_wiki/</a></li>\r
-<li><a href="https://www.simantics.org/members/">www.simantics.org/members/</a></li>\r
-<li><a href="https://www.simantics.org">www.simantics.org</a></li>\r
+<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
</ul>\r
-</li>\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
+<h1>Release Schedule</h1>\r
+<ul>\r
+<li>Releases are branched 4 weeks before the set release date.</li>\r
+<li>During this time no more new features are allowed in the release branch and the existing work shall be stabilized. Work must be focused on bug fixes and documentation.</li>\r
+<li>Source code changes to release branches are forbidden in the last 2 weeks. Documentation-only changes are still allowed. However, if critical show-stopper problems surface during that time, the changes must be done. After that the release engineering team must decide whether to stick to the original release schedule or whether to delay the release.</li>\r
</ul>\r
-<p>In the following sections each task is described step by step.</p>\r
+<hr />\r
<h1>Simantics Platform Release - Step by Step</h1>\r
<h2>Create release branch from selected commit</h2>\r
<p>When release stabilisation starts, branch <code>simantics/platform</code> and <code>simantics/third-party</code> repositories:</p>\r
<ul>\r
<li><code>simantics.target</code></li>\r
<li><code>org.simantics.sdk.build.targetdefinition.target</code></li>\r
-<li><code>org.simantics.sdk.build.targetdefinition-semantum.target</code></li>\r
</ul>\r
-<p>At the beginning of each .target file, increment <code>sequenceNumber</code> by 1</p>\r
+<p>At the beginning of simantics.target file, increment <code>sequenceNumber</code> by 1</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
</code></pre>\r
-<p>Next, replace the following rows in those files:</p>\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/master/external-components/maven"/>\r
<repository location="http://www.simantics.org/download/master/external-components/manual"/>\r
</ul>\r
</li>\r
</ul>\r
+<p>Running these two builds will ensure that both the external components required to build the SDK and the Simantics SDK for the new release branch are published online at <code>http://www.simantics.org/download/release/x.y.z[.w]/</code>.</p>\r
+<p>After this, whenever changes are pushed/merged to <code>release/x.y.z[.w]</code> branch in Gerrit, new <strong>SDK/Simantics SDK</strong> builds are triggered automatically and they will publish the results at the same location online.</p>\r
+<p>This means that one does not have to do any tricks after this to build and publish the SDK as a P2 repository online. It is an automated process that is performed by the <a href="https://www.simantics.org/jenkins/job/SDK/job/Simantics%20SDK/">SDK/Simantics SDK</a> Jenkins job.</p>\r
<h2>Review documentation</h2>\r
<p>Documentation to review:</p>\r
<ul>\r
<li><a href="http://dev.simantics.org/">Developer wiki</a></li>\r
-<li><a href="http://www.simantics.org/end_user_wiki">End-user wiki</a></li>\r
-<li><a href="http://www.simantics.org/members">Member wiki</a></li>\r
+<li><a href="https://www.simantics.org/end_user_wiki">End-user wiki</a></li>\r
+<li><a href="https://www.simantics.org/members">Member wiki</a></li>\r
</ul>\r
<p>For each wiki page:</p>\r
<ul>\r
<p>Note The -m argument must be supplied to create an <a href="https://git-scm.com/book/en/v2/Git-Basics-Tagging">annotated tag</a>.\r
Only annotated or signed tags can be pushed to Gerrit.</p>\r
</blockquote>\r
-<h2>Dump documentation wikis</h2>\r
-<p>Dump documentation wiki using <a href="./dump-wikis.sh">dump-wikis.sh</a> script.</p>\r
-<p>The wiki documentation is mainly in MediaWiki installations. The only\r
-sane way to tag the documentation is to back up the mysql database\r
-backing the wiki.</p>\r
+<h2>Backup documentation wiki databases</h2>\r
+<p>This step is only necessary for major/minor releases, not for service releases.</p>\r
+<p>The wiki databases to be backed up are:</p>\r
+<ul>\r
+<li><a href="http://dev.simantics.org/">Developer wiki</a></li>\r
+<li><a href="https://www.simantics.org/end_user_wiki">End-user wiki</a></li>\r
+</ul>\r
+<p>These are MediaWiki installations. The only sane way to "tag" the documentation\r
+is to back up the mysql database backing the wiki. Should the wiki be required\r
+at a later time for some reason, we'll put the documentation up then in a\r
+separate Mediawiki installation.</p>\r
+<p>Dump documentation wiki databases using <a href="./dump-wikis.sh">dump-wikis.sh</a> script.</p>\r
<h2>Compile change log entry</h2>\r
<ul>\r
<li>Edit the <a href="https://www.simantics.org/redmine/projects/simantics-platform/wiki/ChangeLog">main page</a> and add a a link for release x.y.z[.w].</li>\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="https://www.simantics.org">simantics.org</a>: Post news on the release and a link to the redmine post</li>\r
-<li><a href="http://dev.simantics.org">dev wiki</a>: Update roadmap at http://dev.simantics.org/index.php/Roadmap</li>\r
-<li><a href="mailto:simantics-developers@simantics.org">simantics-developers@simantics.org</a> Send mail to simantics-developers:</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>Mail template:</strong></p>\r
+<p><strong>Newsletter template:</strong></p>\r
<pre><code>Hello everyone,\r
\r
Simantics release x.y.z[.w] has been released. Head over to\r
Best regards,\r
Simantics Release Engineering Team\r
</code></pre>\r
-<p><strong>News entry template:</strong></p>\r
-<pre><code>On <date> Simantics x.y.z[.w] was tagged in SVN. Please find change log at:\r
-* [[simantics-platform:Simantics_xyzw|Simantics x.y.z.w]]\r
+<p><strong>Redmine news template:</strong></p>\r
+<pre><code>Title: Simantics x.y.z[.w] released\r
+\r
+Simantics x.y.z[.w] was released on <date>.\r
+Please find change log at: [[simantics-platform:Simantics_xyzw|Simantics x.y.z[.w]]]\r
\r
Insert some general thoughts on the release...\r
</code></pre>\r
<hr />\r
<h1>TODO</h1>\r
<ul>\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
-<li>Create a parametrized release train pipeline build in Jenkins that creates all artifacts of a simantics release in one go</li>\r
-<li>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.</li>\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
+</ul>\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
</ul>\r
\r
</body>\r
Code Review / simantics / platform.git / blobdiff