aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSteve Mynott <steve.mynott@gmail.com>2016-10-16 10:31:02 +0100
committerSteve Mynott <steve.mynott@gmail.com>2016-10-16 10:31:02 +0100
commite017ba0b6bb42b3a2849fabf6e2a34d6abc97871 (patch)
treeb0a7ad0ba41df9af7cf2e113187b16d3e517df4e
parent8ea8fb8edec479406c1868a22b3e226dadc4a524 (diff)
semi automate the module changelog creation for announcement
-rw-r--r--tools/star/release-guide.pod10
1 files changed, 9 insertions, 1 deletions
diff --git a/tools/star/release-guide.pod b/tools/star/release-guide.pod
index 5dc9a7a..fb0c54a 100644
--- a/tools/star/release-guide.pod
+++ b/tools/star/release-guide.pod
@@ -95,11 +95,16 @@ name to the modules/MODULES.txt file.
Verify that all of the git submodules are at the desired commit
for the Star release. To bring all modules up to the current
-'master' branch, one can do
+'master' branch, one can do:
# pull master in each submodule dir
$ git submodule foreach git pull origin master
+Create a temporary file as a basis for module changelog to be
+included in release announcement below:
+
+ $ git diff --submodule=log origin/master..HEAD > /tmp/mod.txt
+
Then you may commit your update of the submodules:
# commit submodules state to star repo
@@ -117,6 +122,9 @@ to any changes listed in Rakudo's ChangeLog.
$ git add docs/announce/YYYY.MM.md
$ git commit docs
+The module changelog temporary file above can be used to help with
+the corresponding section in the announcement.
+
At this point it is strongly advised that you push your changes so far, to get
feedback on your announcement while you do other steps.