From: levitte <levitte@b62f149e-849f-11dd-9899-c7ba65f7c4c7>
Date: Mon, 9 Mar 2009 22:28:09 +0000 (+0000)
Subject: Use the same releasing notes as for yubico-core here
X-Git-Tag: yubikey-personalisation_0.97-1~121
X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=96dbe509f7c39fffddb97efd24573ca5d8d6b749;p=yubikey-personalization.old

Use the same releasing notes as for yubico-core here

git-svn-id: https://yubikey-personalization.googlecode.com/svn/trunk@41 b62f149e-849f-11dd-9899-c7ba65f7c4c7
---

diff --git a/notes/make-release.txt b/notes/make-release.txt
new file mode 100644
index 0000000..853e30d
--- /dev/null
+++ b/notes/make-release.txt
@@ -0,0 +1,30 @@
+== THIS NEEDS TO BE FILLED IN ==
+
+In every release, the following steps need to be taken:
+
+1.   Update the version information in the following files:
+
+     - configure.ac	You MUST change the version number given to
+			AC_INIT.
+
+1.5. To make life simpler, you might want to start a shell and define
+     a version variable as follows (change 'x.y' to the version number
+     that you set in configure.ac):
+
+     $ RELEASE=x.y
+
+     If you don't do this, you will have to replace "$RELEASE" with
+     the version number manually every time it's mentioned in the
+     commands following.
+
+2. Commit a revision with the changed files and a message noting what
+   is done, as follows:
+
+   $ svn ci -m "Release $RELEASE" configure.ac
+
+3. Tag the release as follows:
+
+   $ svn copy https://yubikey-personalization.googlecode.com/svn/trunk \
+              https://yubikey-personalization.googlecode.com/svn/tags/release-$RELEASE \
+           -m "Tagging release $RELEASE of yubico-personalization."
+