From 3130aa4bd31eb5b0ce0d1bba53d68ed7e236df55 Mon Sep 17 00:00:00 2001 From: Karl Ramm Date: Wed, 30 Nov 2011 02:15:56 -0500 Subject: release armature --- NOTES | 4 ---- README | 25 ------------------------- README.in | 25 +++++++++++++++++++++++++ release | 28 ++++++++++++++++++++++++++++ 4 files changed, 53 insertions(+), 29 deletions(-) delete mode 100644 README create mode 100644 README.in create mode 100755 release diff --git a/NOTES b/NOTES index d9920d1..7a125d6 100644 --- a/NOTES +++ b/NOTES @@ -25,7 +25,3 @@ itself. Thus, we use __STDC__ (both in h/sysdep.h and in zephyr.h) to guess whether the compiler will handle const, prototypes, and stdarg. This is unfortunately not as reliable as using autoconf features like AC_C_CONST. - -The Zephyr system version number is kept in server/version.c, and -should be updated when releases are made. - diff --git a/README b/README deleted file mode 100644 index 78c33b2..0000000 --- a/README +++ /dev/null @@ -1,25 +0,0 @@ -This is a 3.0.1 release candidate of the Project Athena Zephyr -notification system. - -Zephyr allows users to send messages to other users or to groups of -users. Users can view incoming Zephyr messages as windowgrams -(transient X windows) or as text on a terminal. Zephyr can optionally -make use of the Kerberos version 4 security library or the Hesiod -service name resolution library. - -Bug reports or patches should go to bug-zephyr@mit.edu. Please do not -send questions about snapshots; they are not supported. - -To find out how to configure, build, and install Zephyr, read the file -INSTALL. - -To find out how to operate a Zephyr service, read the file OPERATING. - -To find out how to use an existing Zephyr service, read the file -USING. - -Please read the file NOTES before making any modifications to the -source tree. - ---Karl Ramm -http://zephyr.1ts.org/ diff --git a/README.in b/README.in new file mode 100644 index 0000000..9011c94 --- /dev/null +++ b/README.in @@ -0,0 +1,25 @@ +This is version @VERSION@ of the Project Athena Zephyr +notification system. + +Zephyr allows users to send messages to other users or to groups of +users. Users can view incoming Zephyr messages as windowgrams +(transient X windows) or as text on a terminal. Zephyr can optionally +make use of the Kerberos version 4 security library or the Hesiod +service name resolution library. + +Bug reports or patches should go to bug-zephyr@mit.edu. Please do not +send questions about snapshots; they are not supported. + +To find out how to configure, build, and install Zephyr, read the file +INSTALL. + +To find out how to operate a Zephyr service, read the file OPERATING. + +To find out how to use an existing Zephyr service, read the file +USING. + +Please read the file NOTES before making any modifications to the +source tree. + +--Karl Ramm +http://zephyr.1ts.org/ diff --git a/release b/release new file mode 100755 index 0000000..caf8bcd --- /dev/null +++ b/release @@ -0,0 +1,28 @@ +#!/bin/sh -x + +VERSION=$1 +if test -z "$VERSION"; then + echo $0: usage: $0 version + exit 1 +fi + +if test -n "$(git status --porcelain)"; then + echo $0: git status is wordy, you probably want to stash and note your branch + exit 2 +fi +git tag $VERSION -m 'release $VERSION' +git checkout --detach +git clean -fxd +git rm .gitignore +git rm -r debian +git rm release +echo $VERSION > VERSION +sed -e "s/@VERSION@/$VERSION/" README.in > README +git rm README.in +libtoolize -ic +autoreconf +git add -A +git commit -m "release $VERSION" +git tag release/$VERSION -m "release $VERSION processed for git archive" + +git checkout master -- cgit v1.2.3