FYI:
>From f65304f3cff63b4759c6f783adf1fe41688fe776 Mon Sep 17 00:00:00 2001
From: Jim Meyering <[email protected]>
Date: Sat, 13 Feb 2010 10:04:44 +0100
Subject: [PATCH] doc: update release procedure to account for soname version
number
* README-release: Add a step "0", and update step 3 to match reality.
---
README-release | 11 +++++++----
1 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/README-release b/README-release
index 7b7fcd1..a6f46a1 100644
--- a/README-release
+++ b/README-release
@@ -1,4 +1,8 @@
-Here is most of the steps we (maintainers) follow when making a release.
+Here are most of the steps a maintainer followas when making a release.
+
+0. Adjust the shared library version number in libparted/Makefile.am.
+ See the three variables there, CURRENT, REVISION, AGE, and follow
+ the guidelines in "info libtool".
1. Execute build-aux/parted-release. `parted-release --help` contains
additional information.
@@ -7,8 +11,8 @@ Here is most of the steps we (maintainers) follow when making
a release.
builds and passes all tests.
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
+ Start with the generated template in ~/announce-parted-$VERSION.
+ Remember to include a description 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
@@ -25,4 +29,3 @@ Here is most of the steps we (maintainers) follow when making
a release.
To: [email protected], [email protected]
Cc: [email protected], [email protected]
Subject: parted-$VERSION released [stable]
-
--
1.7.0.rc2.170.gbc565
_______________________________________________
parted-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/parted-devel
