release: automate and document

Add a brief description of how to release initscripts. Also automate
the creation of the tarball using "make release".

Signed-off-by: Tom Gundersen <teg@jklm.no>

3 files changed, 27 insertions, 2 deletions

diff --git a/.gitignore b/.gitignore
index c601da6..d07d3f9 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,4 +1,5 @@
 minilogd
 minilogd.o
 tags
-*.pkg.tar.*
+*.tar.xz*
+pkg/
diff --git a/Makefile b/Makefile
index 520700b..0ec54ee 100644
--- a/Makefile
+++ b/Makefile
@@ -1,4 +1,10 @@
-minilogd: minilogd.o
+VER:=$(shell sh -c 'git describe')
+
+minilogd:
+	minilogd.o
 
 clean:
 	rm -f minilogd minilogd.o
+
+release:
+	git archive HEAD --prefix=initscripts-$(VER)/ | xz > initscripts-$(VER).tar.xz
diff --git a/RELEASE b/RELEASE
new file mode 100644
index 0000000..786b286
--- /dev/null
+++ b/RELEASE
@@ -0,0 +1,18 @@
+Releasing
+
+1) create an anotated tag on the format YYYY.MM.X, where YYYY is the year,
+   MM is the month and X is a number starting from 1. E.g.:
+
+	$ git tag -a 2011.04.1
+
+2) create a tarball
+
+	$ make release
+
+3) copy the tarball to gerolde
+
+	$ scp initscripts-YYYY.MM.X.tar.xz gerolde.archlinux.org:/srv/ftp/other/initscripts/
+
+4) check that the PKGBUILD in git is in sync with the PKGBUILD to be released
+
+5) create packages for both arches and push to testing