Release engineering doc now reflects simupedia git move.

[simantics/platform.git] / releng / doc / release.html

diff --git a/releng/doc/release.html b/releng/doc/release.html
index 17c7d28f45016120cb6736611260a8f2e648e55a..aaccfc9152e0da5fdae61f9e56275cee47dac70e 100644 (file)
--- a/releng/doc/release.html
+++ b/releng/doc/release.html
@@ -332,7 +332,7 @@ img {
 <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
@@ -478,7 +478,7 @@ refs #yyyy
 <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://&lt;user&gt;@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 &quot;Simantics x.y.z[.w] simultaneous release&quot;\r
 git push origin --tags\r
@@ -556,15 +556,15 @@ separate Mediawiki installation.</p>
 </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 &quot;newsletter&quot; 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/&lt;news number&gt;\r
 for the release news.\r
@@ -583,6 +583,9 @@ Insert some general thoughts on the release...
 <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
@@ -590,12 +593,7 @@ Insert some general thoughts on the release...
 </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