simantics/platform
and simantics/third-party
Git repositories have a branch release/x.y.z[.w]
and tag x.y.z[.w]
.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.
Plug-in components that are part of the release train:
Products 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.
When release stabilisation starts, branch simantics/platform
and simantics/third-party
repositories:
git clone ssh://<user>@www.simantics.org:29418/simantics/platform.git
cd platform
git branch release/x.y.z[.w] <commit>
git push origin release/x.y.z[.w]
git clone ssh://<user>@www.simantics.org:29418/simantics/third-party.git
cd third-party
git branch release/x.y.z[.w] <commit>
git push origin release/x.y.z[.w]
When creating major/minor releases <commit>
is usually a commit in the master
branch.
With service releases, branch from an existing release/*
branch instead.
In release 1.31.0 Simantics started using uses the wonderful tool from Obeo (https://github.com/mbarbero/fr.obeo.releng.targetplatform) to generate .target
files from .tpd
files which allow much simpler specification of the target contents and also composition of .tpd files via inclusion.
In the following steps, it is recommended to ensure every .target
file is up-to-date by regenerating them from .tpd
files. While doing so, take care to use up-to-date online contents to perform the generation.
.tpd
filesRetrieve release branch of the platform repository
git clone ssh://<user>@www.simantics.org:29418/simantics/platform.git
cd platform
git branch release/x.y.z[.w] remotes/origin/release/x.y.z[.w]
git checkout release/x.y.z[.w]
Edit all target platform files in releng/org.simantics.sdk.build.targetdefinition/
, i.e.
org.simantics.sdk.build.targetdefinition.tpd
simantics.tpd
Replace the following rows in both mentioned files:
location "http://www.simantics.org/download/master/external-components/maven" {
location "http://www.simantics.org/download/master/external-components/manual" {
include "http://www.simantics.org/download/master/org.simantics.sdk.build.targetdefinition.tpd"
location "http://www.simantics.org/download/master/sdk" {
with
location "http://www.simantics.org/download/release/x.y.z[.w]/maven" {
location "http://www.simantics.org/download/release/x.y.z[.w]/manual" {
include "http://www.simantics.org/download/release/x.y.z[.w]/org.simantics.sdk.build.targetdefinition.tpd"
location "http://www.simantics.org/download/release/x.y.z[.w]/sdk" {
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.
release/x.y.z[.w]
true
release/x.y.z[.w]
true
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.
.target
filesLastly, we want to change the .target
files to point to the correct P2 repository locations. This happens by opening the previously edited .tpd
files in Obeo's editor and regenerating the .target
files by pressing Alt+R.
Push the changed files to remote again with commit message:
Configured release/x.y.z[.w] branch .target files.
refs #xxxx
Trigger an execution of the simantics-release-train Jenkins job with parameters
release/x.y.z[.w]
true
to ensure that all components of the release train build fine and to publish first versions of P2 repositories of everything online.
Documentation to review:
For each wiki page:
Ensure tutorial wiki documentation at http://dev.simantics.org/index.php/Tutorials is up-to-date with the released platform
Ensure tutorial projects and product build properly
com.acme.movie
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
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
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] 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.
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.
\t
) with |
with Regular Expressions
selection checked|#
|
%{background: lightsalmon}Major Bug%
%{background: lightgreen}Major Feature%
%{background: lightgreen}Major Enhancement%
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.
Best regards,
Simantics Release Engineering Team
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...