From 2edbcde78ebb706b9bc5919e04b7312ec655c48d Mon Sep 17 00:00:00 2001 From: brarcher Date: Tue, 5 Nov 2013 02:09:13 +0000 Subject: [PATCH] update svn URL in release process git-svn-id: svn+ssh://svn.code.sf.net/p/check/code/trunk@852 64e312b2-a51f-0410-8e61-82d0ca0eb02a --- HACKING | 2 +- Makefile.am | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/HACKING b/HACKING index 35e0d57..768080d 100644 --- a/HACKING +++ b/HACKING @@ -43,7 +43,7 @@ If you are behind a proxy remember to "socksify" (or similar) your based on r637 (2012-10-22 13:54:14 +0200)" Now 'svn commit -m "* Update for release" NEWS' 5. make SF_USERNAME=username RELEASE_VERSION=X.Y.Z preparerelease - This will tag trunk as https://svn.sourceforge.net/svnroot/check/tags/check-X.Y.Z + This will tag trunk as https://svn.code.sf.net/p/check/code/tags/check-X.Y.Z 6. Follow the prompts. If anything goes wrong see Makefile.am and complete it by hand. 7. Use the following template to announce the release: ===== diff --git a/Makefile.am b/Makefile.am index 3aedf1b..e966c76 100644 --- a/Makefile.am +++ b/Makefile.am @@ -69,8 +69,8 @@ releasevars: preparerelease: releasevars .svnrelease prereleasecheck @echo tagging release from `cat .svnrelease` - svn cp -m "Tagging for check-${RELEASE_VERSION}" -r`cat .svnrelease` https://check.svn.sourceforge.net/svnroot/check/trunk https://check.svn.sourceforge.net/svnroot/check/tags/check-${RELEASE_VERSION} - svn co https://check.svn.sourceforge.net/svnroot/check/tags/check-${RELEASE_VERSION} check-${RELEASE_VERSION} + svn cp -m "Tagging for check-${RELEASE_VERSION}" -r`cat .svnrelease` https://svn.code.sf.net/p/check/code/trunk https://svn.code.sf.net/p/check/code/tags/check-${RELEASE_VERSION} + svn co https://svn.code.sf.net/p/check/code/tags/check-${RELEASE_VERSION} check-${RELEASE_VERSION} @echo "Any last minute changes? This is your final chance." @echo "CTRL-D when finished or 'exit 1' to abort." @echo "aborting will leave the partially prepared release in" `pwd` -- 2.49.0