aurora-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject aurora git commit: Document how to generate a changelog
Date Mon, 12 Sep 2016 10:57:42 GMT
Repository: aurora
Updated Branches:
  refs/heads/master c7f710a56 -> b429612ef

Document how to generate a changelog

Let's pass on that druid knowledge from one release manager to the next.

Reviewed at


Branch: refs/heads/master
Commit: b429612ef8ead04db0b16ca2dbf1e5ae76521e42
Parents: c7f710a
Author: Stephan Erb <>
Authored: Mon Sep 12 12:57:10 2016 +0200
Committer: Stephan Erb <>
Committed: Mon Sep 12 12:57:10 2016 +0200

 docs/development/ | 7 +++++++
 1 file changed, 7 insertions(+)
diff --git a/docs/development/ b/docs/development/
index 14f3b52..ebf464b 100644
--- a/docs/development/
+++ b/docs/development/
@@ -56,6 +56,13 @@ must have access to commit to the dist.a.o repositories.
 1. Ensure that all issues resolved for this release candidate are tagged with the correct
 Version in JIRA, the changelog script will use this to generate the CHANGELOG in step #2.
+To assign the fix version:
+    * Look up the [previous release date](
+    * Query all issues resolved after that release date: `project = AURORA AND status in
(resolved, Closed) and fixVersion is empty and resolutiondate >= "YYYY/MM/DD"`
+    * In the upper right corner of the query result, select Tools > Bulk Edit.
+    * Select all issues > edit issue > set 'Change Fix Version/s' to the release version.
+    * Make sure to uncheck 'Send mail for this update' at the bottom.
 2. Create a release candidate. This will automatically update the CHANGELOG and commit it,
create a
 branch and update the current version within the trunk. To create a minor version update
and publish

View raw message