aboutsummaryrefslogtreecommitdiff
path: root/doc/developers/release-new-version
diff options
context:
space:
mode:
authorcweiske <cweiske@b3834d28-1941-0410-a4f8-b48e95affb8f>2009-11-17 20:19:44 +0000
committercweiske <cweiske@b3834d28-1941-0410-a4f8-b48e95affb8f>2009-11-17 20:19:44 +0000
commit1565780efea67c584f6d1f60af28af47168ee22f (patch)
tree3e289a46028a8cd7da892c7d7e1ef55825f18913 /doc/developers/release-new-version
parenta527c584f895e38a00ce384a897d4393c880c442 (diff)
downloadsemanticscuttle-1565780efea67c584f6d1f60af28af47168ee22f.tar.gz
semanticscuttle-1565780efea67c584f6d1f60af28af47168ee22f.tar.bz2
remove svn tag instructions; phing does it
git-svn-id: https://semanticscuttle.svn.sourceforge.net/svnroot/semanticscuttle/trunk@556 b3834d28-1941-0410-a4f8-b48e95affb8f
Diffstat (limited to 'doc/developers/release-new-version')
-rw-r--r--doc/developers/release-new-version2
1 files changed, 0 insertions, 2 deletions
diff --git a/doc/developers/release-new-version b/doc/developers/release-new-version
index 7529d1a..33a3ef6 100644
--- a/doc/developers/release-new-version
+++ b/doc/developers/release-new-version
@@ -14,8 +14,6 @@ How to release a new version of SemanticScuttle
tasks.
Run "phing release", and it will upload the release to
sourceforge and create a svn tag.
-5. Tag the release in svn:
- svn cp https://semanticscuttle.svn.sourceforge.net/svnroot/semanticscuttle/trunk https://semanticscuttle.svn.sourceforge.net/svnroot/semanticscuttle/tags/$version
6. Write announcement mail to the SemanticScuttle mailing list
semanticscuttle-devel@lists.sourceforge.net
7. Announce the new release in the sourceforge project news