Differences

This shows you the differences between two versions of the page.

--- mantisbt:release_process [2021/03/07 19:15] – [Source Forge] Upload with rsync dregad
+++ mantisbt:release_process [2022/05/10 10:07] (current) – [Packaging the Release] asc files are ascii-armored signature files dregad
@@ Line 86: / Line 86: @@
 ===== Cutting the Release =====
-  * Create an annotated, GPG-signed tag in Git; the tag should be formatted as "release-1.x.x" \\ \\
+  * Create an annotated, GPG-signed tag in Git; the tag should be formatted as ''release-M.N.P'' (e.g. 2.25.4) \\ \\
      * For **stable releases** <code>
-$ git checkout master-1.M.x
+$ git checkout master-M.N
-$ VERSION=1.M.N
+$ VERSION=M.N.P
 $ git tag -s release-$VERSION -m "Stable release $VERSION"
 </code> Note: If this fails, see below for tag signing troubleshooting
     * For **development releases** (e.g. alpha, beta, release candidates) <code>
 $ git checkout master
-$ VERSION=1.M.N
+$ VERSION=M.N.P
 $ git tag -s release-$VERSION -m "Development release $VERSION"
 </code>
@@ Line 102: / Line 102: @@
 </code>
-  * In case we are starting a new stable branch, also create it using the format "master-1.x.x": <code>
+  * In case we are starting a new stable branch, also create it using the format "master-M.N": <code>
-$ git branch master-1.x.x master
+$ git branch master-M.N master
-$ git push origin master-1.x.x
+$ git push origin master-M.N
 </code>
@@ Line 135: / Line 135: @@
 Generate release tarballs using the ''buildrelease-repo.py'' script found in the ''mantisbt-tools.git'' repository:
 <code>
-$ /build/buildrelease-repo.py --fresh --docbook --ref release-$VERSION /path/to/output
+$ /build/buildrelease-repo.py --fresh --docbook --ref release-$VERSION --clean /path/to/output
 </code>
-This will create a //.zip// and //.tar.gz// tarball of the release, and create a //.digest// file for each tarball with //md5// and //sha1// hashes, all in the ''/path/to/output'' directory specified in the command.  The ''--docbook'' option will automatically build single-file versions of the manuals into the tarball's ''/doc'' directory.
+This will create the following files in the ''/path/to/output'' directory specified in the command.
-[dregad] the script also creates '.asc' files, which are not documented in SourceForge section - what to do with them ?
+  * a //.zip// and //.tar.gz// tarball of the release
+  * a //.digest// file for each tarball with //md5// and, //sha*// hashes
+  * an ASCII-armored GPG signature file for each tarball (with //.asc// extension)
+The ''--docbook'' option will automatically build single-file versions of the manuals into the tarball's ''/doc'' directory.
@@ Line 253: / Line 257: @@
     * manually via SourceForge's File Manager web interface, or
     * with rsync (//USERNAME// is your SourceForge user ID) <code>
-$ rsync -vP -rsh ssh /path/to/output/* USERNAME@frs.sourceforge.net:/home/frs/project/mantisbt/mantis-stable/$VERSION
+$ rsync -vP --rsh=ssh /path/to/output/* USERNAME@frs.sourceforge.net:/home/frs/project/mantisbt/mantis-stable/$VERSION
 </code>
   * Download the release off SF.net and verify correctness.
@@ Line 263: / Line 267: @@
   * Blog: Post an announcement
+  * Gitter: Post an announcement
+The notifications below require accounts that only vboctor has access to...
   * Twitter: announce the release via mantisbt twitter account.
   * Update mailing list based on official bug tracker users since users can now signup to our bugtracker to get such announcements.