summaryrefslogtreecommitdiff
path: root/README-release
diff options
context:
space:
mode:
authorJoel Granados Moreno <jgranado@redhat.com>2009-07-27 11:12:30 +0200
committerJoel Granados Moreno <jgranado@redhat.com>2009-07-27 19:11:24 +0200
commitc736ece2d4b28f3b300cda689fd86f5138478d86 (patch)
tree358d470ef2e12a1e50d600f992e2d7cb24326b99 /README-release
parent1b766b697b7347c7818c8b4aebc2a77c3cf5fa23 (diff)
downloadparted-c736ece2d4b28f3b300cda689fd86f5138478d86.tar.gz
Minor corrections to the release README.
* README-release: Change "$v" to "$VERSION", its more explicit. Include a reminder to add the definition of parted to the release mail.
Diffstat (limited to 'README-release')
-rw-r--r--README-release4
1 files changed, 3 insertions, 1 deletions
diff --git a/README-release b/README-release
index 1668706..7b7fcd1 100644
--- a/README-release
+++ b/README-release
@@ -8,6 +8,8 @@ Here is most of the steps we (maintainers) follow when making a release.
3. Write the release announcement that will be posted to the mailing lists.
There is a template generated at /tmp/announce-parted-$VERSION.
+ Remember to include the definition of parted. You can find this at
+ http://www.gnu.org/software/parted/index.shtml
4. Run the gnupload command that was suggested by the release script. You can
find this at the end of release.log.
@@ -22,5 +24,5 @@ Here is most of the steps we (maintainers) follow when making a release.
7. Send the gpg-signed announcement mail, e.g.,
To: info-gnu@gnu.org, parted-devel@lists.alioth.debian.org
Cc: coordinator@translationproject.org, bug-parted@gnu.org
- Subject: parted-$v released [stable]
+ Subject: parted-$VERSION released [stable]