From: Tuukka Lehtonen 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. When the release branches are ready for the release, tag them with the tag
@@ -478,7 +478,7 @@ refs #yyyy
Tag release/* branches
vx.y.z[.w]
:git clone ssh://<user>@www.simantics.org:29418/simantics/platform.git
-cd platform
+cd platform
git checkout release/x.y.z[.w]
git tag vx.y.z[.w] -m "Simantics x.y.z[.w] simultaneous release"
git push origin --tags
@@ -556,15 +556,15 @@ separate Mediawiki installation.
Newsletter template:
Hello everyone,
-
+
Simantics release x.y.z[.w] has been released. Head over to
https://www.simantics.org/redmine/news/<news number>
for the release news.
@@ -583,6 +583,9 @@ Insert some general thoughts on the release...
TODO
+- Start using https://github.com/mbarbero/fr.obeo.releng.targetplatform to generate
.target
files. .tpd
files allow specifying version ranges instead of specific versions.
+
+
- Create a parametrized release train pipeline build in Jenkins that creates all artifacts of a simantics release
- Desktop, Sysdyn, R, Simupedia, FMIL, FMI Studio
@@ -590,12 +593,7 @@ Insert some general thoughts on the release...
--
-
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
-
--
-
Start using https://github.com/mbarbero/fr.obeo.releng.targetplatform to generate .target
files. .tpd
files allow specifying version ranges instead of specific versions.
-
+- 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