aboutsummaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
authorMoritz Lenz <moritz@faui2k3.org>2013-02-25 21:28:42 +0100
committerMoritz Lenz <moritz@faui2k3.org>2013-02-25 21:28:42 +0100
commit2284987cd1b6c886148b6ab50ead7b2cccc9ec99 (patch)
treed01f7f1a6c885d79dcb462bf1326444eb1591cc9 /tools
parent1a8aae4933a78670c17291f77a9f14de00a205eb (diff)
markdown template for release announcement, uvtc++
makes it easier to convert to HTML for the rakudo.org wordpress blog
Diffstat (limited to 'tools')
-rw-r--r--tools/star/release-guide.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/tools/star/release-guide.pod b/tools/star/release-guide.pod
index 0c273b4..efb2864 100644
--- a/tools/star/release-guide.pod
+++ b/tools/star/release-guide.pod
@@ -64,13 +64,13 @@ for the Star release. To bring all modules up to the current
=item 6.
If one doesn't already exist, create a release announcement in
-docs/announce/YYYY.MM . You can often use the previous release's
+docs/announce/YYYY.MM.md . You can often use the previous release's
file as a starting point, updating the release number, version
information, name, etc. as appropriate. Be sure to pay attention
to any changes listed in Rakudo's ChangeLog.
- $ vi docs/announce/YYYY.MM
- $ git add docs/announce/YYYY.MM
+ $ vi docs/announce/YYYY.MM.md
+ $ git add docs/announce/YYYY.MM.md
$ git commit docs
=item 7.