* README-release: Change "$v" to "$VERSION", its more explicit. Include
a reminder to add the definition of parted to the release mail.
---
README-release | 4 +++-
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: [email protected], [email protected]
Cc: [email protected], [email protected]
- Subject: parted-$v released [stable]
+ Subject: parted-$VERSION released [stable]
--
1.6.0.6
_______________________________________________
parted-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/parted-devel
