diff options
| author | Christian Weiske <cweiske@cweiske.de> | 2011-05-26 08:20:04 +0200 |
|---|---|---|
| committer | Christian Weiske <cweiske@cweiske.de> | 2011-05-26 08:20:04 +0200 |
| commit | 18989f97f1c4299f447b011c28961ca5c8310c13 (patch) | |
| tree | 3ecf5ac1572f064d461209514d1568f216536839 /doc/developers/release-new-version.rst | |
| parent | b279ded75769818ae78ca11654ecef935d6cb956 (diff) | |
| download | semanticscuttle-18989f97f1c4299f447b011c28961ca5c8310c13.tar.gz semanticscuttle-18989f97f1c4299f447b011c28961ca5c8310c13.tar.bz2 | |
documentation index
Diffstat (limited to 'doc/developers/release-new-version.rst')
| -rw-r--r-- | doc/developers/release-new-version.rst | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/developers/release-new-version.rst b/doc/developers/release-new-version.rst new file mode 100644 index 0000000..4b2540a --- /dev/null +++ b/doc/developers/release-new-version.rst @@ -0,0 +1,22 @@ +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 doc/UPGRADE.txt +3. Update version in data/templates/about.tpl.php, + build.xml and doc/README.txt +4. Create a release zip file via the build script: + Just type "phing". +5. Make a test installation from your zip file with a fresh + database. Register a user, add bookmarks etc. +6. When all is fine, it's time to release. + The build script takes care for most of the + tasks. + Run "phing release", and it will upload the release to + sourceforge and create a svn tag. +7. Write announcement mail to the SemanticScuttle mailing list + semanticscuttle-devel@lists.sourceforge.net +8. Announce the new release in the sourceforge project news + https://sourceforge.net/apps/trac/sourceforge/wiki/News + |