Recent changes to ASF Release Guidelines

ASF Release Guidelines modified by Dave Brondsema

Dave Brondsema — Mon, 06 Nov 2023 20:16:51 -0000

--- v26
+++ v27
@@ -20,8 +20,8 @@
     * Issue tracker clean (no open issues for this release).
 * After successful vote
     * send a \[RESULT] \[VOTE] email
-    * move release files from /dev/ to /release/ like:  (change numbers)
-        * `svnmucc -U https://dist.apache.org/repos/dist/ mv dev/allura/allura-1.3.2.tar.gz release/allura/allura-1.3.2.tar.gz mv dev/allura/allura-1.3.2.tar.gz.asc release/allura/allura-1.3.2.tar.gz.asc mv dev/allura/allura-1.3.2.tar.gz.sha512 release/allura/allura-1.3.2.tar.gz.sha512 -m "Move allura 1.3.2 from dev to release"`
+    * move release files from /dev/ to /release/ like:  (change number at beginning, run from any dir)
+        * `export VER=1.16.0; svnmucc -U https://dist.apache.org/repos/dist/ mv dev/allura/allura-$VER.tar.gz release/allura/allura-$VER.tar.gz mv dev/allura/allura-$VER.tar.gz.asc release/allura/allura-$VER.tar.gz.asc mv dev/allura/allura-$VER.tar.gz.sha512 release/allura/allura-$VER.tar.gz.sha512 -m "Move allura $VER from dev to release"`
     * make a tracker milestone for the release and move the relevant closed tickets ([this search](https://forge-allura.apache.org/p/allura/tickets/search/?q=status%3Aclosed+%26%26+_milestone%3Aunreleased) minus any completed after the release) from "unreleased" into the new milestone for the release
     * push the git tag
     * wait for release to show up on https://dlcdn.apache.org/allura/
@@ -30,6 +30,6 @@
         * wikipedia page has been removed and restored again, could happen again.  See https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/Apache_Allura
     * Add release data to the https://reporter.apache.org/addrelease.html?allura
     * Announce (to dev@allura.a.o and users@allura.a.o and announce@a.o)
-    * Remove old release (it is automatically archived) like: (change numbers)
-        * `svnmucc -U https://dist.apache.org/repos/dist/release/allura rm allura-1.3.1.tar.gz rm allura-1.3.1.tar.gz.asc rm allura-1.3.1.tar.gz.sha512 -m "Remove allura 1.3.1 release"`
+    * Remove old release (it is automatically archived) like: (change number at beginning, run from any dir)
+        * `export OLDVER=1.15.0; svnmucc -U https://dist.apache.org/repos/dist/release/allura rm allura-$OLDVER.tar.gz rm allura-$OLDVER.tar.gz.asc rm allura-$OLDVER.tar.gz.sha512 -m "Remove allura $OLDVER release"`

ASF Release Guidelines modified by Dave Brondsema

Dave Brondsema — Fri, 08 Sep 2023 13:57:59 -0000

--- v25
+++ v26
@@ -1,8 +1,11 @@
 [TOC]

-Use `scripts/asf-release.sh` which builds a proper release and hashes and email template.
-
-
+* Prerequisites for script:
+    * have PGP keys set up according to https://infra.apache.org/new-committers-guide.html#set-up-security-and-pgp-keys
+        * verify it shows up on https://people.apache.org/keys/committer/ and https://downloads.apache.org/allura/KEYS Those only get updated daily
+    * if on mac, `brew install coreutils` and make sure its on your path
+    * have a python virtualenv active (like the Allura one, or at least have `requests gitpython six`  installed)
+* Use `scripts/asf-release.sh` which builds a proper release and hashes and email template.
 * When voting on dev@allura, include details of what was tested.  E.g.:
     * Sums and sigs OK (log below).
     * Build from source tarball succeeds and passes tests on \[list platforms].

ASF Release Guidelines modified by Dave Brondsema

Dave Brondsema — Fri, 23 Sep 2022 16:16:03 -0000

--- v24
+++ v25
@@ -21,10 +21,10 @@
         * `svnmucc -U https://dist.apache.org/repos/dist/ mv dev/allura/allura-1.3.2.tar.gz release/allura/allura-1.3.2.tar.gz mv dev/allura/allura-1.3.2.tar.gz.asc release/allura/allura-1.3.2.tar.gz.asc mv dev/allura/allura-1.3.2.tar.gz.sha512 release/allura/allura-1.3.2.tar.gz.sha512 -m "Move allura 1.3.2 from dev to release"`
     * make a tracker milestone for the release and move the relevant closed tickets ([this search](https://forge-allura.apache.org/p/allura/tickets/search/?q=status%3Aclosed+%26%26+_milestone%3Aunreleased) minus any completed after the release) from "unreleased" into the new milestone for the release
     * push the git tag
-    * wait for release to show up on a few mirrors
-    * Update download links: allura.apache.org [repo](https://forge-allura.apache.org/p/allura/website/), wiki [Home], [wikipedia](https://en.wikipedia.org/wiki/Apache_Allura)
+    * wait for release to show up on https://dlcdn.apache.org/allura/
+    * On allura.apache.org [repo](https://forge-allura.apache.org/p/allura/website/), update download link and add news item highlighting new features
+    * Update download links:  wiki [Home], [wikipedia](https://en.wikipedia.org/wiki/Apache_Allura)
         * wikipedia page has been removed and restored again, could happen again.  See https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/Apache_Allura
-    * Add news item to allura site, highlighting new features
     * Add release data to the https://reporter.apache.org/addrelease.html?allura
     * Announce (to dev@allura.a.o and users@allura.a.o and announce@a.o)
     * Remove old release (it is automatically archived) like: (change numbers)

ASF Release Guidelines modified by Dave Brondsema

Dave Brondsema — Mon, 07 Oct 2019 15:56:07 -0000

--- v23
+++ v24
@@ -17,16 +17,16 @@
     * Issue tracker clean (no open issues for this release).
 * After successful vote
     * send a \[RESULT] \[VOTE] email
-    * move release files from /dev/ to /release/
+    * move release files from /dev/ to /release/ like:  (change numbers)
         * `svnmucc -U https://dist.apache.org/repos/dist/ mv dev/allura/allura-1.3.2.tar.gz release/allura/allura-1.3.2.tar.gz mv dev/allura/allura-1.3.2.tar.gz.asc release/allura/allura-1.3.2.tar.gz.asc mv dev/allura/allura-1.3.2.tar.gz.sha512 release/allura/allura-1.3.2.tar.gz.sha512 -m "Move allura 1.3.2 from dev to release"`
-    * Remove old release (it is automatically archived)
-        * `svnmucc -U https://dist.apache.org/repos/dist/release/allura rm allura-1.3.1.tar.gz rm allura-1.3.1.tar.gz.asc rm allura-1.3.1.tar.gz.sha512 -m "Remove allura 1.3.1 release"`
     * make a tracker milestone for the release and move the relevant closed tickets ([this search](https://forge-allura.apache.org/p/allura/tickets/search/?q=status%3Aclosed+%26%26+_milestone%3Aunreleased) minus any completed after the release) from "unreleased" into the new milestone for the release
     * push the git tag
     * wait for release to show up on a few mirrors
-    * Update download links: allura.apache.org [repo](https://forge-allura.apache.org/p/allura/website/), wiki [Home], [wikipedia](https://en.wikipedia.org/wiki/Apache_Allura), and https://sourceforge.net/projects/allura/files/ (requires SF staff)
+    * Update download links: allura.apache.org [repo](https://forge-allura.apache.org/p/allura/website/), wiki [Home], [wikipedia](https://en.wikipedia.org/wiki/Apache_Allura)
         * wikipedia page has been removed and restored again, could happen again.  See https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/Apache_Allura
     * Add news item to allura site, highlighting new features
     * Add release data to the https://reporter.apache.org/addrelease.html?allura
     * Announce (to dev@allura.a.o and users@allura.a.o and announce@a.o)
+    * Remove old release (it is automatically archived) like: (change numbers)
+        * `svnmucc -U https://dist.apache.org/repos/dist/release/allura rm allura-1.3.1.tar.gz rm allura-1.3.1.tar.gz.asc rm allura-1.3.1.tar.gz.sha512 -m "Remove allura 1.3.1 release"`

ASF Release Guidelines modified by Dave Brondsema

Dave Brondsema — Mon, 24 Sep 2018 19:40:40 -0000

--- v22
+++ v23
@@ -16,14 +16,13 @@
     * CHANGES entry is current.
     * Issue tracker clean (no open issues for this release).
 * After successful vote
-    * send a [RESULT] [VOTE] email
+    * send a \[RESULT] \[VOTE] email
     * move release files from /dev/ to /release/
         * `svnmucc -U https://dist.apache.org/repos/dist/ mv dev/allura/allura-1.3.2.tar.gz release/allura/allura-1.3.2.tar.gz mv dev/allura/allura-1.3.2.tar.gz.asc release/allura/allura-1.3.2.tar.gz.asc mv dev/allura/allura-1.3.2.tar.gz.sha512 release/allura/allura-1.3.2.tar.gz.sha512 -m "Move allura 1.3.2 from dev to release"`
     * Remove old release (it is automatically archived)
         * `svnmucc -U https://dist.apache.org/repos/dist/release/allura rm allura-1.3.1.tar.gz rm allura-1.3.1.tar.gz.asc rm allura-1.3.1.tar.gz.sha512 -m "Remove allura 1.3.1 release"`
-    * make a tracker milestone for the release and move the relevant closed tickets from "unreleased" into the new milestone for the release
+    * make a tracker milestone for the release and move the relevant closed tickets ([this search](https://forge-allura.apache.org/p/allura/tickets/search/?q=status%3Aclosed+%26%26+_milestone%3Aunreleased) minus any completed after the release) from "unreleased" into the new milestone for the release
     * push the git tag
-        * if that's all you push, the forge-allura server currently doesn't pick up on new tags, and you'll need to tweak `/var/local/deploy.sh` on the server so it runs unconditionally, then tweak it back
     * wait for release to show up on a few mirrors
     * Update download links: allura.apache.org [repo](https://forge-allura.apache.org/p/allura/website/), wiki [Home], [wikipedia](https://en.wikipedia.org/wiki/Apache_Allura), and https://sourceforge.net/projects/allura/files/ (requires SF staff)
         * wikipedia page has been removed and restored again, could happen again.  See https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/Apache_Allura

ASF Release Guidelines modified by Dave Brondsema

Dave Brondsema — Mon, 24 Sep 2018 19:31:13 -0000

--- v21
+++ v22
@@ -18,9 +18,9 @@
 * After successful vote
     * send a [RESULT] [VOTE] email
     * move release files from /dev/ to /release/
-        * `svnmucc -U https://dist.apache.org/repos/dist/ mv dev/allura/allura-1.3.2.tar.gz release/allura/allura-1.3.2.tar.gz mv dev/allura/allura-1.3.2.tar.gz.asc release/allura/allura-1.3.2.tar.gz.asc mv dev/allura/allura-1.3.2.tar.gz.sha1 release/allura/allura-1.3.2.tar.gz.sha1 mv dev/allura/allura-1.3.2.tar.gz.sha512 release/allura/allura-1.3.2.tar.gz.sha512 -m "Move allura 1.3.2 from dev to release"`
+        * `svnmucc -U https://dist.apache.org/repos/dist/ mv dev/allura/allura-1.3.2.tar.gz release/allura/allura-1.3.2.tar.gz mv dev/allura/allura-1.3.2.tar.gz.asc release/allura/allura-1.3.2.tar.gz.asc mv dev/allura/allura-1.3.2.tar.gz.sha512 release/allura/allura-1.3.2.tar.gz.sha512 -m "Move allura 1.3.2 from dev to release"`
     * Remove old release (it is automatically archived)
-        * `svnmucc -U https://dist.apache.org/repos/dist/release/allura rm allura-1.3.1.tar.gz rm allura-1.3.1.tar.gz.asc rm allura-1.3.1.tar.gz.sha1 rm allura-1.3.1.tar.gz.sha512 -m "Remove allura 1.3.1 release"`
+        * `svnmucc -U https://dist.apache.org/repos/dist/release/allura rm allura-1.3.1.tar.gz rm allura-1.3.1.tar.gz.asc rm allura-1.3.1.tar.gz.sha512 -m "Remove allura 1.3.1 release"`
     * make a tracker milestone for the release and move the relevant closed tickets from "unreleased" into the new milestone for the release
     * push the git tag
         * if that's all you push, the forge-allura server currently doesn't pick up on new tags, and you'll need to tweak `/var/local/deploy.sh` on the server so it runs unconditionally, then tweak it back

ASF Release Guidelines modified by Dave Brondsema

Dave Brondsema — Wed, 14 Mar 2018 19:32:00 -0000

--- v20
+++ v21
@@ -18,9 +18,9 @@
 * After successful vote
     * send a [RESULT] [VOTE] email
     * move release files from /dev/ to /release/
-        * `svnmucc -U https://dist.apache.org/repos/dist/ mv dev/allura/allura-1.3.2.tar.gz release/allura/allura-1.3.2.tar.gz mv dev/allura/allura-1.3.2.tar.gz.asc release/allura/allura-1.3.2.tar.gz.asc mv dev/allura/allura-1.3.2.tar.gz.md5 release/allura/allura-1.3.2.tar.gz.md5 mv dev/allura/allura-1.3.2.tar.gz.sha1 release/allura/allura-1.3.2.tar.gz.sha1 mv dev/allura/allura-1.3.2.tar.gz.sha512 release/allura/allura-1.3.2.tar.gz.sha512 -m "Move allura 1.3.2 from dev to release"`
+        * `svnmucc -U https://dist.apache.org/repos/dist/ mv dev/allura/allura-1.3.2.tar.gz release/allura/allura-1.3.2.tar.gz mv dev/allura/allura-1.3.2.tar.gz.asc release/allura/allura-1.3.2.tar.gz.asc mv dev/allura/allura-1.3.2.tar.gz.sha1 release/allura/allura-1.3.2.tar.gz.sha1 mv dev/allura/allura-1.3.2.tar.gz.sha512 release/allura/allura-1.3.2.tar.gz.sha512 -m "Move allura 1.3.2 from dev to release"`
     * Remove old release (it is automatically archived)
-        * `svnmucc -U https://dist.apache.org/repos/dist/release/allura rm allura-1.3.1.tar.gz rm allura-1.3.1.tar.gz.asc rm allura-1.3.1.tar.gz.md5 rm allura-1.3.1.tar.gz.sha1 rm allura-1.3.1.tar.gz.sha512 -m "Remove allura 1.3.1 release"`
+        * `svnmucc -U https://dist.apache.org/repos/dist/release/allura rm allura-1.3.1.tar.gz rm allura-1.3.1.tar.gz.asc rm allura-1.3.1.tar.gz.sha1 rm allura-1.3.1.tar.gz.sha512 -m "Remove allura 1.3.1 release"`
     * make a tracker milestone for the release and move the relevant closed tickets from "unreleased" into the new milestone for the release
     * push the git tag
         * if that's all you push, the forge-allura server currently doesn't pick up on new tags, and you'll need to tweak `/var/local/deploy.sh` on the server so it runs unconditionally, then tweak it back

ASF Release Guidelines modified by Dave Brondsema

Dave Brondsema — Thu, 15 Dec 2016 15:06:40 -0000

--- v19
+++ v20
@@ -25,8 +25,8 @@
     * push the git tag
         * if that's all you push, the forge-allura server currently doesn't pick up on new tags, and you'll need to tweak `/var/local/deploy.sh` on the server so it runs unconditionally, then tweak it back
     * wait for release to show up on a few mirrors
-    * Update download links: allura.apache.org [repo](https://forge-allura.apache.org/p/allura/website/), wiki [Home], https://sourceforge.net/projects/allura/files/ (requires SF staff)
-        * wikipedia page has been removed, see https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/Apache_Allura
+    * Update download links: allura.apache.org [repo](https://forge-allura.apache.org/p/allura/website/), wiki [Home], [wikipedia](https://en.wikipedia.org/wiki/Apache_Allura), and https://sourceforge.net/projects/allura/files/ (requires SF staff)
+        * wikipedia page has been removed and restored again, could happen again.  See https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/Apache_Allura
     * Add news item to allura site, highlighting new features
     * Add release data to the https://reporter.apache.org/addrelease.html?allura
     * Announce (to dev@allura.a.o and users@allura.a.o and announce@a.o)

ASF Release Guidelines modified by Dave Brondsema

Dave Brondsema — Tue, 23 Aug 2016 14:27:03 -0000

--- v18
+++ v19
@@ -23,6 +23,7 @@
         * `svnmucc -U https://dist.apache.org/repos/dist/release/allura rm allura-1.3.1.tar.gz rm allura-1.3.1.tar.gz.asc rm allura-1.3.1.tar.gz.md5 rm allura-1.3.1.tar.gz.sha1 rm allura-1.3.1.tar.gz.sha512 -m "Remove allura 1.3.1 release"`
     * make a tracker milestone for the release and move the relevant closed tickets from "unreleased" into the new milestone for the release
     * push the git tag
+        * if that's all you push, the forge-allura server currently doesn't pick up on new tags, and you'll need to tweak `/var/local/deploy.sh` on the server so it runs unconditionally, then tweak it back
     * wait for release to show up on a few mirrors
     * Update download links: allura.apache.org [repo](https://forge-allura.apache.org/p/allura/website/), wiki [Home], https://sourceforge.net/projects/allura/files/ (requires SF staff)
         * wikipedia page has been removed, see https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/Apache_Allura

ASF Release Guidelines modified by Dave Brondsema

Dave Brondsema — Mon, 22 Aug 2016 19:25:10 -0000

--- v17
+++ v18
@@ -24,7 +24,7 @@
     * make a tracker milestone for the release and move the relevant closed tickets from "unreleased" into the new milestone for the release
     * push the git tag
     * wait for release to show up on a few mirrors
-    * Update download links: allura.apache.org (https://git-wip-us.apache.org/repos/asf?p=allura-site.git;a=shortlog;h=refs/heads/asf-site), wiki [Home], https://sourceforge.net/projects/allura/files/ (requires SF staff)
+    * Update download links: allura.apache.org [repo](https://forge-allura.apache.org/p/allura/website/), wiki [Home], https://sourceforge.net/projects/allura/files/ (requires SF staff)
         * wikipedia page has been removed, see https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/Apache_Allura
     * Add news item to allura site, highlighting new features
     * Add release data to the https://reporter.apache.org/addrelease.html?allura