From 4d7f4125047dd5088fdb69b0c9ae5e61e53bd00c Mon Sep 17 00:00:00 2001
From: Anthony Carrico <acarrico@memebeam.org>
Date: Mon, 24 Feb 2003 19:16:56 +0000
Subject: [PATCH] Get ready for next version.

---
 Makefile     |  2 +-
 NEWS         |  2 ++
 README.admin | 13 +++++++++++++
 3 files changed, 16 insertions(+), 1 deletion(-)
 create mode 100644 README.admin

diff --git a/Makefile b/Makefile
index 4448b2b..18eac53 100644
--- a/Makefile
+++ b/Makefile
@@ -11,7 +11,7 @@ INSTALL_DATA = $(INSTALL) -m 644
 
 .SUFFIXES:
 
-version := 0.1
+version := 0.2
 
 s48-interfaces := $(shell find s48 \
                     -maxdepth 2 -mindepth 2 \
diff --git a/NEWS b/NEWS
index aeff789..a063fe9 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,5 @@
+version 0.2
+
 version 0.1 - 2003-03-24
 
 * Initial release.
diff --git a/README.admin b/README.admin
new file mode 100644
index 0000000..f4ee042
--- /dev/null
+++ b/README.admin
@@ -0,0 +1,13 @@
+How to make a release:
+
+1. Make sure NEWS is up-to-date (at least add the distribution date).
+2. Check out a clean source tree from cvs.
+3. Make the distribution:
+  make dist
+4. Test the distribution.
+5. Tag the release. For example to tag sunterlib-0.1.tar.gz
+  cvs tag sunterlib-0-1 .
+6. Post the release:
+  scp sunterlib-0.1.tar.gz subversions.gnu.org:/upload/sunterlib
+7. Increment the version number in Makefile.
+8. Start a new version entry in NEWS.