</ul>\r
<hr />\r
<h1>Simantics Platform Release - Step by Step</h1>\r
-<h2>Create release branch from selected commit</h2>\r
-<p>When release stabilisation starts, branch all relevant repositories like this:</p>\r
-<pre><code>git clone ssh://<user>@gerrit.simantics.org:29418/simantics/platform.git\r
-cd platform\r
-git branch release/x.y.z[.w] <commit>\r
-git push origin release/x.y.z[.w]\r
-</code></pre>\r
-<p>When creating major/minor releases <code><commit></code> is usually a commit in the <code>master</code> branch.\r
-With service releases, branch from an existing <code>release/*</code> branch instead.</p>\r
-<p>Instead of doing this clone+branch+push sequence for every SDK repository separately,\r
-please use the included <code>release-helper.sh</code> shell script to perform this mechanical work. The script supports many useful basic git commands which all perform the requested operation on all the release train repositories. The operations can be seen from the help text printed by the script when given no arguments:</p>\r
-<pre><code>Usage: release-helper.sh <version> <branch-name> <user-name> clone|branch|checkout|fetch|list-tags|pull|push|push-tags|remove-tag|status|tag\r
-</code></pre>\r
-<p>Always begin by cloning all the repositories for working on</p>\r
-<pre><code>./release-helper.sh x.y.z release/x.y.z your-git-username clone\r
-</code></pre>\r
-<p>This will create a directory called <code>x.y.z</code> under the current working directory and clone all the repositories under it. The first <code><version></code> argument is only used for the base working directory <code>x.y.z</code>. The second <code><branch-name></code> argument tells what branch to specify to the action, i.e. <code>branch</code>, <code>checkout</code>, etc.</p>\r
-<p>Branching and pushing the branches to remote happens as follows:</p>\r
-<pre><code>./release-helper.sh x.y.z release/x.y.z your-git-username branch\r
-./release-helper.sh x.y.z release/x.y.z your-git-username checkout\r
-./release-helper.sh x.y.z release/x.y.z your-git-username push\r
-</code></pre>\r
-<p>If you're creating a service release <code>x.y.w</code> from <code>x.y.z</code> where <code>w > z</code>, do this:</p>\r
-<pre><code>./release-helper.sh x.y.w release/x.y.z your-git-username clone\r
-./release-helper.sh x.y.w release/x.y.z your-git-username checkout\r
-./release-helper.sh x.y.w release/x.y.w your-git-username branch\r
-./release-helper.sh x.y.w release/x.y.w your-git-username checkout\r
-# Perhaps make modifications to the branch here and commit to each project separately\r
-./release-helper.sh x.y.w release/x.y.w your-git-username push\r
-</code></pre>\r
-<h2>Prepare release branch for use</h2>\r
-<p>In release 1.31.0 Simantics started using the wonderful tool from Obeo (<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 from <code>.tpd</code> files which allow much simpler specification of the target contents and also composition of .tpd files via inclusion.</p>\r
-<p>In the following steps, it is recommended to ensure every <code>.target</code> file is up-to-date by regenerating them from <code>.tpd</code> files. While doing so, take care to use up-to-date online contents to perform the generation.</p>\r
-<h3>Prepare <code>.tpd</code> files in platform repository</h3>\r
-<ol start="0">\r
-<li>\r
-<p>Ensure you've ran</p>\r
-<pre><code>./release-helper.sh x.y.z release/x.y.z your-git-username checkout\r
-</code></pre>\r
-<p>to make sure you're working on the release branch before doing anything.</p>\r
-</li>\r
-<li>\r
-<p>Go into the cloned platform repository at <code>x.y.z/platform</code></p>\r
-</li>\r
-<li>\r
-<p>Edit all target platform files in <code>releng/org.simantics.sdk.build.targetdefinition/</code>, i.e.</p>\r
-<ul>\r
-<li><code>org.simantics.sdk.build.targetdefinition.tpd</code></li>\r
-<li><code>simantics.tpd</code></li>\r
-</ul>\r
-<p>Replace the following rows in both mentioned files:</p>\r
-<pre><code>location "http://www.simantics.org/download/master/external-components/maven" {\r
-location "http://www.simantics.org/download/master/external-components/manual" {\r
-include "http://www.simantics.org/download/master/org.simantics.sdk.build.targetdefinition.tpd"\r
-location "http://www.simantics.org/download/master/sdk" {\r
-</code></pre>\r
-<p>with</p>\r
-<pre><code>location "http://www.simantics.org/download/release/x.y.z[.w]/maven" {\r
-location "http://www.simantics.org/download/release/x.y.z[.w]/manual" {\r
-include "http://www.simantics.org/download/release/x.y.z[.w]/org.simantics.sdk.build.targetdefinition.tpd"\r
-location "http://www.simantics.org/download/release/x.y.z[.w]/sdk" {\r
-</code></pre>\r
-</li>\r
-<li>\r
-<p>Edit version number of <code>org.simantics.sdk</code> feature in <code>features/org.simantics.sdk.feature/feature.xml</code> to <code>x.y.z</code>.</p>\r
-<pre><code><feature\r
- id="org.simantics.sdk"\r
- label="Simantics SDK"\r
- version="x.y.z"\r
- provider-name="VTT Technical Research Centre of Finland">\r
-</code></pre>\r
-<p>If the release branch you're setting up is a hotfix-release <code>x.y.z.w</code>,\r
-don't include the <code>.w</code> part in this version.</p>\r
-<p>An example of these changes can be seen in\r
-<a href="https://gerrit.simantics.org/r/gitweb?p=simantics%2Fplatform.git;a=commit;h=5271b0faa98303225d00e6cd838d3fc52488545c">gitweb</a>\r
-or <a href="https://gerrit.simantics.org/r/#/c/1361/">review 1361</a>.</p>\r
-</li>\r
-<li>\r
+<h2>Create release engineering issue(s) in Gitlab</h2>\r
<p>Ensure that Gitlab has a release engineering issue for the branched release,\r
such as <a href="https://gitlab.simantics.org/simantics/platform/issues/16">Simantics 1.34.0 release engineering</a></p>\r
<ul>\r
<li>Add a link to the previous previous release's issue in the new issue description, e.g. <code>simantics/platform#16</code>.</li>\r
<li>Add labels <code>releng</code> and <code>$version</code> to the new issue</li>\r
</ul>\r
-</li>\r
-</ol>\r
-<ol start="5">\r
-<li>\r
-<p>Commit the changes made</p>\r
-<pre><code> git commit -a\r
+<h2>Create release branch from selected commit</h2>\r
+<p>When release stabilisation starts, all relevant repositories need to be branched.\r
+When creating major/minor releases <code><commit></code> is usually a commit in the <code>master</code> branch.\r
+With service releases, branch from an existing <code>release/*</code> branch instead.</p>\r
+<p>Instead of doing this clone+branch+push sequence for every SDK repository separately, please use the included <code>release-helper.sh</code> shell script to perform this mechanical work.\r
+The script supports many useful basic git commands which all perform the requested operation on all the release train repositories.\r
+The operations can be seen from the help text printed by the script when given no arguments:</p>\r
+<pre><code>Usage: release-helper.sh <version> <branch-name> <user-name> <command> [<command-arguments>]\r
+\r
+Commands:\r
+ clone The first thing that needs to be done before anything else\r
+ Clones all platform repositories under directory <version>\r
+\r
+Inspection commands:\r
+ diff [args] Run git diff [args] for each platform repository\r
+ log [args] Run git log [args] for each platform repository\r
+ status [args] Run git status [args] for each platform repository\r
+ list-tags Run git tag -l for each repository\r
+\r
+Action:\r
+ add\r
+ branch Run git branch <branch-name> for each platform repository\r
+ checkout Run git checkout <branch-name> for each repository\r
+ commit\r
+ fetch Run git fetch --all for each repository\r
+ pull Run git pull --all for each repository\r
+ push Run git push origin <branch> for each repository\r
+ push-tags Run git push --tags for each repository\r
+ remove-tag Run git tag -d v<branch> for each repository\r
+ reset [args] Run git reset [args] for each repository\r
+ tag Run git checkout <branch> and\r
+ git tag -a v<branch> -m "Simantics <branch> simultaneous release"\r
+ for each repository\r
+\r
+Compound release commands:\r
+ prepare-release-branch <from-branch>\r
+ <from-branch> the name of the branch that the codebase is currently on\r
+\r
+Top-level release commands:\r
+ bump-master-version <from-version> <to-version>\r
+ <from-version> the version string to replace\r
+ <to-version> the replacing new version string\r
+\r
+ branch-release <from-branch>\r
+ <from-branch> the branch to create the service branch from\r
+ e.g. master or release/x.y.z\r
</code></pre>\r
-<p>with the commit message</p>\r
-<pre><code> Configured release/x.y.z[.w] branch for SDK builds.\r
-\r
- gitlab #xxxx\r
+<p>Begin by cloning all the repositories for working on</p>\r
+<pre><code>user=<your-git-username>\r
+version=x.y.z\r
+branch=release/x.y.z\r
+./release-helper.sh $version $branch $user clone\r
</code></pre>\r
-<p>where <code>#xxxx</code> is the number of the x.y.z[.w] release engineering issue and push them to remote</p>\r
-<pre><code> git push origin release/x.y.z[.w]\r
+<p>This will create a directory called <code>x.y.z</code> under the current working directory and clone all the repositories under it.\r
+The first <code>version</code> argument is only used for the base working directory <code>x.y.z</code>.\r
+The second <code>branch</code> argument tells what branch to specify to some of the available actions, e.g. <code>branch</code>, <code>checkout</code>, etc.</p>\r
+<p>Creating the release branch from master and pushing the new branches to remote happens as follows:</p>\r
+<pre><code># When the commit messages appear, add references to created\r
+# Gitlab release engineering issues by adding this to the commit message:\r
+# \r
+# gitlab #xxxx\r
+#\r
+# where xxxx is the release engineering issue for the respective project\r
+./release-helper.sh $version $branch $user branch-release master\r
+./release-helper.sh $version $branch $user push\r
</code></pre>\r
-</li>\r
-<li>\r
-<p>If you are branching from <code>master</code>, bump the revision of master right now to start the next release cycle in master.\r
-An example of these changes can be seen in <a href="https://gerrit.simantics.org/r/gitweb?p=simantics%2Fplatform.git;a=commit;h=564ac84a2949b19ce5c1c7c838b575527ec42b09">gitweb</a> or in <a href="https://gerrit.simantics.org/r/#/c/1362">review 1362</a>. The changes include:</p>\r
+<p>If you're creating a service release <code>x.y.w</code> from <code>x.y.z</code> where <code>w > z</code>, do this:</p>\r
+<pre><code>fromBranch=release/x.y.z\r
+branch=release/x.y.w\r
+./release-helper.sh $version $branch $user branch-release $fromBranch\r
+./release-helper.sh $version $branch $user push\r
+</code></pre>\r
+<p>If you branched a new release from <code>master</code>, you should also bump the revision of the master branch right now to start the next release cycle in master.\r
+An example of these changes can be seen in <a href="https://gerrit.simantics.org/r/gitweb?p=simantics%2Fplatform.git;a=commit;h=564ac84a2949b19ce5c1c7c838b575527ec42b09">gitweb</a> or in <a href="https://gerrit.simantics.org/r/#/c/1362">review 1362</a>.\r
+The changes include:</p>\r
<ul>\r
<li>Simantics Desktop splash screen update (version number)</li>\r
<li>Simantics target platform name to state correct development version</li>\r
<li>org.simantics.sdk feature version bump</li>\r
<li>org.simantics.sdk.repository project version bump</li>\r
</ul>\r
-<p>Commit the changes with the following commit message</p>\r
-<pre><code>Bumped master target and org.simantics.sdk feature versions to x.y.z[.w].\r
-\r
-gitlab #yyyy\r
+<p>Perform and push the changes by running:</p>\r
+<pre><code>./release-helper.sh $version $branch $user bump-master-version 1.35.0 1.36.0\r
+./release-helper.sh $version $branch $user push\r
</code></pre>\r
-<p>where <code>#yyyy</code> is the number of the next release's release engineering issue.</p>\r
-</li>\r
-<li>\r
-<p>Do the same for simupedia target platform files as was done in task 6.\r
-for platform target definitions.</p>\r
-</li>\r
-</ol>\r
<h3>Test Release Train build</h3>\r
<p>Trigger an execution of the <a href="https://www.simantics.org/jenkins/job/simantics-release-train/">simantics-release-train</a> Jenkins job with parameters</p>\r
<ul>\r
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.
Core components of the release train:
-* External third party library dependencies required by the platform - [simantics/third-party.git](https://gerrit.simantics.org/r/gitweb?p=simantics/third-party.git;a=summary)\r
-* The Simantics Platform - [simantics/platform.git](https://gerrit.simantics.org/r/gitweb?p=simantics/platform.git;a=summary)\r
+* External third party library dependencies required by the platform - [simantics/third-party.git](https://gerrit.simantics.org/r/gitweb?p=simantics/third-party.git;a=summary)
+* The Simantics Platform - [simantics/platform.git](https://gerrit.simantics.org/r/gitweb?p=simantics/platform.git;a=summary)
Plug-in components that are part of the release train:
* Simupedia - [members/simupedia.git](https://gerrit.simantics.org/r/gitweb?p=members/simupedia.git;a=summary)
# Simantics Platform Release - Step by Step
-## Create release branch from selected commit
+## Create release engineering issue(s) in Gitlab
-When release stabilisation starts, branch all relevant repositories like this:
+Ensure that Gitlab has a release engineering issue for the branched release,
+such as [Simantics 1.34.0 release engineering](https://gitlab.simantics.org/simantics/platform/issues/16)
+* Make a new release issue with title `$version release engineering`.
+* Add a link to the previous previous release's issue in the new issue description, e.g. `simantics/platform#16`.
+* Add labels `releng` and `$version` to the new issue
- git clone ssh://<user>@gerrit.simantics.org:29418/simantics/platform.git
- cd platform
- git branch release/x.y.z[.w] <commit>
- git push origin release/x.y.z[.w]
+## Create release branch from selected commit
+When release stabilisation starts, all relevant repositories need to be branched.
When creating major/minor releases `<commit>` is usually a commit in the `master` branch.
With service releases, branch from an existing `release/*` branch instead.
-Instead of doing this clone+branch+push sequence for every SDK repository separately,
-please use the included `release-helper.sh` shell script to perform this mechanical work. The script supports many useful basic git commands which all perform the requested operation on all the release train repositories. The operations can be seen from the help text printed by the script when given no arguments:
-
- Usage: release-helper.sh <version> <branch-name> <user-name> clone|branch|checkout|fetch|list-tags|pull|push|push-tags|remove-tag|status|tag
-
-Always begin by cloning all the repositories for working on
-
- ./release-helper.sh x.y.z release/x.y.z your-git-username clone
-
-This will create a directory called `x.y.z` under the current working directory and clone all the repositories under it. The first `<version>` argument is only used for the base working directory `x.y.z`. The second `<branch-name>` argument tells what branch to specify to the action, i.e. `branch`, `checkout`, etc.
-
-Branching and pushing the branches to remote happens as follows:
-
- ./release-helper.sh x.y.z release/x.y.z your-git-username branch
- ./release-helper.sh x.y.z release/x.y.z your-git-username checkout
- ./release-helper.sh x.y.z release/x.y.z your-git-username push
+Instead of doing this clone+branch+push sequence for every SDK repository separately, please use the included `release-helper.sh` shell script to perform this mechanical work.
+The script supports many useful basic git commands which all perform the requested operation on all the release train repositories.
+The operations can be seen from the help text printed by the script when given no arguments:
+
+```
+Usage: release-helper.sh <version> <branch-name> <user-name> <command> [<command-arguments>]
+
+Commands:
+ clone The first thing that needs to be done before anything else
+ Clones all platform repositories under directory <version>
+
+Inspection commands:
+ diff [args] Run git diff [args] for each platform repository
+ log [args] Run git log [args] for each platform repository
+ status [args] Run git status [args] for each platform repository
+ list-tags Run git tag -l for each repository
+
+Action:
+ add
+ branch Run git branch <branch-name> for each platform repository
+ checkout Run git checkout <branch-name> for each repository
+ commit
+ fetch Run git fetch --all for each repository
+ pull Run git pull --all for each repository
+ push Run git push origin <branch> for each repository
+ push-tags Run git push --tags for each repository
+ remove-tag Run git tag -d v<branch> for each repository
+ reset [args] Run git reset [args] for each repository
+ tag Run git checkout <branch> and
+ git tag -a v<branch> -m "Simantics <branch> simultaneous release"
+ for each repository
+
+Compound release commands:
+ prepare-release-branch <from-branch>
+ <from-branch> the name of the branch that the codebase is currently on
+
+Top-level release commands:
+ bump-master-version <from-version> <to-version>
+ <from-version> the version string to replace
+ <to-version> the replacing new version string
+
+ branch-release <from-branch>
+ <from-branch> the branch to create the service branch from
+ e.g. master or release/x.y.z
+```
+
+Begin by cloning all the repositories for working on
+
+ user=<your-git-username>
+ version=x.y.z
+ branch=release/x.y.z
+ ./release-helper.sh $version $branch $user clone
+
+This will create a directory called `x.y.z` under the current working directory and clone all the repositories under it.
+The first `version` argument is only used for the base working directory `x.y.z`.
+The second `branch` argument tells what branch to specify to some of the available actions, e.g. `branch`, `checkout`, etc.
+
+Creating the release branch from master and pushing the new branches to remote happens as follows:
+
+ # When the commit messages appear, add references to created
+ # Gitlab release engineering issues by adding this to the commit message:
+ #
+ # gitlab #xxxx
+ #
+ # where xxxx is the release engineering issue for the respective project
+ ./release-helper.sh $version $branch $user branch-release master
+ ./release-helper.sh $version $branch $user push
If you're creating a service release `x.y.w` from `x.y.z` where `w > z`, do this:
- ./release-helper.sh x.y.w release/x.y.z your-git-username clone
- ./release-helper.sh x.y.w release/x.y.z your-git-username checkout
- ./release-helper.sh x.y.w release/x.y.w your-git-username branch
- ./release-helper.sh x.y.w release/x.y.w your-git-username checkout
- # Perhaps make modifications to the branch here and commit to each project separately
- ./release-helper.sh x.y.w release/x.y.w your-git-username push
-
-## Prepare release branch for use
-
-In release 1.31.0 Simantics started using the wonderful tool from Obeo ([https://github.com/mbarbero/fr.obeo.releng.targetplatform](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.
-
-### Prepare `.tpd` files in platform repository
-
-0. Ensure you've ran\r
-
- ./release-helper.sh x.y.z release/x.y.z your-git-username checkout
-
- to make sure you're working on the release branch before doing anything.
-
-1. Go into the cloned platform repository at `x.y.z/platform`\r
-
-2. 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:
+ fromBranch=release/x.y.z
+ branch=release/x.y.w
+ ./release-helper.sh $version $branch $user branch-release $fromBranch
+ ./release-helper.sh $version $branch $user push
- ~~~
- 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" {
- ~~~
-
-3. Edit version number of `org.simantics.sdk` feature in `features/org.simantics.sdk.feature/feature.xml` to `x.y.z`.
- ~~~
- <feature
- id="org.simantics.sdk"
- label="Simantics SDK"
- version="x.y.z"
- provider-name="VTT Technical Research Centre of Finland">
- ~~~
-
- If the release branch you're setting up is a hotfix-release `x.y.z.w`,
- don't include the `.w` part in this version.
-
- An example of these changes can be seen in
- [gitweb](https://gerrit.simantics.org/r/gitweb?p=simantics%2Fplatform.git;a=commit;h=5271b0faa98303225d00e6cd838d3fc52488545c)
- or [review 1361](https://gerrit.simantics.org/r/#/c/1361/).
-
-4. Ensure that Gitlab has a release engineering issue for the branched release,
- such as [Simantics 1.34.0 release engineering](https://gitlab.simantics.org/simantics/platform/issues/16)
- * Make a new release issue with title `$version release engineering`.
- * Add a link to the previous previous release's issue in the new issue description, e.g. `simantics/platform#16`.
- * Add labels `releng` and `$version` to the new issue
-
-
-5. Commit the changes made
-
- git commit -a
-
- with the commit message
-
- Configured release/x.y.z[.w] branch for SDK builds.
-
- gitlab #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]
-
-6. 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](https://gerrit.simantics.org/r/gitweb?p=simantics%2Fplatform.git;a=commit;h=564ac84a2949b19ce5c1c7c838b575527ec42b09) or in [review 1362](https://gerrit.simantics.org/r/#/c/1362). The changes include:
+If you branched a new release from `master`, you should also bump the revision of the master branch right now to start the next release cycle in master.
+An example of these changes can be seen in [gitweb](https://gerrit.simantics.org/r/gitweb?p=simantics%2Fplatform.git;a=commit;h=564ac84a2949b19ce5c1c7c838b575527ec42b09) or in [review 1362](https://gerrit.simantics.org/r/#/c/1362).
+The changes include:
* Simantics Desktop splash screen update (version number)
* Simantics target platform name to state correct development version
* org.simantics.sdk feature version bump
* org.simantics.sdk.repository project version bump
- Commit the changes with the following commit message
-
- Bumped master target and org.simantics.sdk feature versions to x.y.z[.w].
-
- gitlab #yyyy
-
- where `#yyyy` is the number of the next release's release engineering issue.
+Perform and push the changes by running:
-7. Do the same for simupedia target platform files as was done in task 6.\r
- for platform target definitions.
+ ./release-helper.sh $version $branch $user bump-master-version 1.35.0 1.36.0
+ ./release-helper.sh $version $branch $user push
### Test Release Train build
Code Review / simantics / platform.git / commitdiff