X-Git-Url: https://gerrit.simantics.org/r/gitweb?a=blobdiff_plain;ds=inline;f=releng%2Fdoc%2Frelease.html;h=aaccfc9152e0da5fdae61f9e56275cee47dac70e;hb=eedebb7f1831267ed4dbc20cc78d5bea95098ac2;hp=126c76cd889489ed514ec46d3e8111b771850cf6;hpb=70d2af523cf495a41ad1ef5a40ec56c7362e59e2;p=simantics%2Fplatform.git diff --git a/releng/doc/release.html b/releng/doc/release.html index 126c76cd8..aaccfc915 100644 --- a/releng/doc/release.html +++ b/releng/doc/release.html @@ -297,8 +297,9 @@ img {
release/x.y.z[.w]
release stabilisation branchThere 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.
+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.
+Products that are part of the release train:
Plug-in components that are part of the release train:
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.
+In the following sections each task is described step by step.
+When release stabilisation starts, branch simantics/platform
and simantics/third-party
repositories:
simantics.target
org.simantics.sdk.build.targetdefinition.target
org.simantics.sdk.build.targetdefinition-semantum.target
At the beginning of each .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 those files:
+Next, replace the following rows in both mentioned files:
<repository location="http://www.simantics.org/download/master/sdk"/>
<repository location="http://www.simantics.org/download/master/external-components/maven"/>
<repository location="http://www.simantics.org/download/master/external-components/manual"/>
@@ -381,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.
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 http://www.simantics.org/download/release/x.y.z[.w]/
.
After this, whenever changes are pushed/merged to release/x.y.z[.w]
branch in Gerrit, new SDK/Simantics SDK builds are triggered automatically and they will publish the results at the same location online.
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 SDK/Simantics SDK Jenkins job.
Documentation to review:
For each wiki page:
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
-Note The -m argument must be supplied to create an annotated tag. Only annotated or signed tags can be pushed to Gerrit.
Dump documentation wiki using dump-wikis.sh script.
-The wiki documentation is mainly in MediaWiki installations. The only -sane way to tag the documentation is to back up the mysql database -backing the wiki.
+This step is only necessary for major/minor releases, not for service releases.
+The wiki databases to be backed up are:
+ +These are MediaWiki installations. The only sane way to "tag" the documentation +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.
+Mail template:
+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.
@@ -509,18 +572,28 @@ for the release news.
Best regards,
Simantics Release Engineering Team
-News entry template:
-On <date> Simantics x.y.z[.w] was tagged in SVN. Please find change log at:
-* [[simantics-platform:Simantics_xyzw|Simantics x.y.z.w]]
+Redmine news template:
+Title: Simantics x.y.z[.w] released
+
+Simantics x.y.z[.w] was released on <date>.
+Please find change log at: [[simantics-platform:Simantics_xyzw|Simantics x.y.z[.w]]]
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
+
+
+
+
- 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
-- Create a parametrized release train pipeline build in Jenkins that creates all artifacts of a simantics release in one go
-- Start using https://github.com/mbarbero/fr.obeo.releng.targetplatform to generate
.target
files. .tpd
files allow specifying version ranges instead of specific versions.