X-Git-Url: https://gerrit.simantics.org/r/gitweb?a=blobdiff_plain;ds=sidebyside;f=releng%2Fdoc%2Frelease.html;h=aaccfc9152e0da5fdae61f9e56275cee47dac70e;hb=bbb298df815caf685630eaa9041fbfd3a1519763;hp=1ede770874c0492dbb73f6ecf834d1fe01a7aeb5;hpb=3448b94a8e90047c88eb62a0542c1596acb701b8;p=simantics%2Fplatform.git diff --git a/releng/doc/release.html b/releng/doc/release.html index 1ede77087..aaccfc915 100644 --- a/releng/doc/release.html +++ b/releng/doc/release.html @@ -332,7 +332,7 @@ img {
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.
simantics.target
org.simantics.sdk.build.targetdefinition.target
At the beginning of simantics.target file, increment sequenceNumber
by 1
At the beginning of simantics.target file, increment sequenceNumber
by 1 and replace
+the version numbers in target name and org.simantics.sdk.feature.group
and
+org.simantics.sdk.source.feature.group
with x.y.z[.w]
:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?pde version="3.8"?>
<target name="Simantics x.y.z[.w]" sequenceNumber="11">
+<unit id="org.simantics.sdk.feature.group" version="x.y.z[.w]"/>
+<unit id="org.simantics.sdk.source.feature.group" version="x.y.z[.w]"/>
Next, replace the following rows in both mentioned files:
<repository location="http://www.simantics.org/download/master/sdk"/>
@@ -391,6 +395,41 @@ git checkout release/x.y.z[.w]
<repository location="http://www.simantics.org/download/release/x.y.z[.w]/external-components/manual"/>
+Edit version number of org.simantics.sdk
feature in features/org.simantics.sdk.feature/feature.xml
to x.y.z[.w]
.
<feature
+ id="org.simantics.sdk"
+ label="Simantics SDK"
+ version="x.y.z"
+ provider-name="VTT Technical Research Centre of Finland">
+
+An example of these changes can be seen in gitweb.
+Ensure that Redmine has a release engineering issue for the branched release, such as Simantics 1.30.0 release engineering. Make a copy of the previous release issue to create the new one. Include link to original issue while copying.
+Commit the changes made
+ git commit -a
+
+with the commit message
+ Configured release/x.y.z[.w] branch for SDK builds.
+
+ refs #xxxx
+
+where #xxxx
is the number of the x.y.z[.w] release engineering issue and push them to remote
git push origin release/x.y.z[.w]
+
+If you are branching from master
, bump the revision of master right now to start the next release cycle in master.
+An example of these changes can be seen in gitweb.
Commit the changes with the following commit message
+Bumped master target and org.simantics.sdk feature versions to x.y.z[.w].
+refs #yyyy
+
+where #yyyy
is the number of the next release's release engineering issue.
When the release branches are ready for the release, tag them with the tag 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] release"
+git tag vx.y.z[.w] -m "Simantics x.y.z[.w] simultaneous release"
git push origin --tags
git clone ssh://<user>@www.simantics.org:29418/simantics/third-party.git
cd third-party
git checkout release/x.y.z[.w]
-git tag vx.y.z[.w] -m "Simantics x.y.z[.w] release"
+git tag vx.y.z[.w] -m "Simantics x.y.z[.w] simultaneous release"
git push origin --tags
@@ -466,7 +505,7 @@ is to back up the mysql database backing the wiki. Should the wiki be required at a later time for some reason, we'll put the documentation up then in a separate Mediawiki installation.-
- Dump documentation wiki databases using [dump-wikis.sh](./dump-wikis.sh) script.
+- Dump documentation wiki databases using dump-wikis.sh script.
- Put the generated backup x.y.z.tar.gz at /var/backup/simantics-releases/x.y.z/wiki/
Compile change log entry
@@ -517,15 +556,15 @@ separate Mediawiki installation.Disseminate information about the release
-
- Developer Wiki: Update roadmap at http://dev.simantics.org/index.php/Roadmap
-- Redmine: Post news on the developer/user-visible changes here.
+- Developer Wiki: Update roadmap at http://dev.simantics.org/index.php/Roadmap
+- Redmine: Post news on the developer/user-visible changes here
- simantics.org: Post news on the release and a link to the redmine post
- Members Wiki: Update frame plan to reflect the realized dates and link to Redmine news
- mailto:simantics-developers@simantics.org Send "newsletter" to `simantics-developers@simantics.org:
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. @@ -544,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
@@ -551,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