X-Git-Url: https://gerrit.simantics.org/r/gitweb?p=simantics%2Fplatform.git;a=blobdiff_plain;f=releng%2Fdoc%2Frelease.html;h=df0f9d70f5cc3da78118f903ebd3e552e905e192;hp=6f0fd975306c2bdf486efac5ef01c1ca685c0247;hb=0659830f76d64f2376fdb39666a5e5ff4e11c2dd;hpb=ae93c9930c6345c32219e6845b9e72e9d9d2d28c
diff --git a/releng/doc/release.html b/releng/doc/release.html
index 6f0fd9753..df0f9d70f 100644
--- a/releng/doc/release.html
+++ b/releng/doc/release.html
@@ -396,15 +396,39 @@ the version numbers in target name and Edit version number of `org.simantics.sdk` feature in `features/org.simantics.sdk.feature/feature.xml` to `x.y.z[.w]`. Edit version number of Now commit and push the changes to the release branch. 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 with the commit message where If you are branching from Commit the changes with the following commit message where org.simantics.sdk.feature.group
-<feature
+
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">
+ git commit -a
+
+ Configured release/x.y.z[.w] branch for SDK builds.
+
+ refs #xxxx
+
#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]
+
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.
+Bumped master target and org.simantics.sdk feature versions to x.y.z[.w].
+refs #yyyy
+
#yyyy
is the number of the next release's release engineering issue.Initialize release branch distribution web site
@@ -481,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.