Updated release engineering documentation.

[simantics/platform.git] / releng / doc / release.md

diff --git a/releng/doc/release.md b/releng/doc/release.md
index 6d55c144db228408b2b2daf2aa1bf96a6b41ade9..b16736e80aeed1e5cef81c33852eed98d0a115ac 100644 (file)
--- a/releng/doc/release.md
+++ b/releng/doc/release.md
@@ -120,6 +120,34 @@ With service releases, branch from an existing `release/*` branch instead.
          provider-name="VTT Technical Research Centre of Finland">
    ~~~
 
+   An example of these changes can be seen in [gitweb](https://www.simantics.org:8088/r/gitweb?p=simantics/platform.git;a=commit;h=bab5c9bd68277c76dc5c20bc7a60a9896cbd1540).
+
+4. Ensure that Redmine has a release engineering issue for the branched release, such as [Simantics 1.30.0 release engineering](https://www.simantics.org/redmine/issues/7263). Make a copy of the previous release issue to create the new one. Include link to original issue while copying.
+
+5. 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]
+
+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://www.simantics.org:8088/r/gitweb?p=simantics/platform.git;a=commitdiff;h=ae93c9930c6345c32219e6845b9e72e9d9d2d28c).
+
+   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.
+
 ### Initialize release branch distribution web site
 
 * Run [SDK/Deploy External Components to Web](https://www.simantics.org/jenkins/job/SDK/job/Deploy%20External%20Components%20to%20Web/) build with parameters: