From 610401ff18f3cca4de897ce2f4c81f1c0457cf5a Mon Sep 17 00:00:00 2001 From: cweiske Date: Fri, 30 Oct 2009 17:54:42 +0000 Subject: Explain how to release a new version git-svn-id: https://semanticscuttle.svn.sourceforge.net/svnroot/semanticscuttle/trunk@479 b3834d28-1941-0410-a4f8-b48e95affb8f --- doc/developers/release-new-version | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/developers/release-new-version (limited to 'doc/developers/release-new-version') diff --git a/doc/developers/release-new-version b/doc/developers/release-new-version new file mode 100644 index 0000000..074e72f --- /dev/null +++ b/doc/developers/release-new-version @@ -0,0 +1,17 @@ +How to release a new version of SemanticScuttle +=============================================== + +0. Run unit tests and verify that all of them pass +1. Update doc/ChangeLog +2. Update version in data/templates/about.tpl.php +3. Create a zip file with all contents, and make sure + the zip file root directory is SemanticScuttle-$version/ +4. Make a test installtion from your zip file with a fresh + database, register, add bookmarks etc. +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. Upload release to sourceforge +7. Write announcement mail to the SemanticScuttle mailing list + semanticscuttle-devel@lists.sourceforge.net +8. Announce the new release in the sourceforge project news + -- cgit v1.2.3