2009-10-30 18:54:42 +01:00
|
|
|
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
|
2009-11-16 20:20:24 +01:00
|
|
|
and build.xml
|
2009-11-14 11:24:08 +01:00
|
|
|
3. Create a release zip file via the build script:
|
|
|
|
|
Just type "phing".
|
|
|
|
|
4. Make a test installation from your zip file with a fresh
|
|
|
|
|
database. Register a user, add bookmarks etc.
|
|
|
|
|
5. 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.
|
2009-10-30 18:54:42 +01:00
|
|
|
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
|
2009-11-14 11:24:08 +01:00
|
|
|
6. Write announcement mail to the SemanticScuttle mailing list
|
2009-10-30 18:54:42 +01:00
|
|
|
semanticscuttle-devel@lists.sourceforge.net
|
2009-11-14 11:24:08 +01:00
|
|
|
7. Announce the new release in the sourceforge project news
|
|
|
|
|
https://sourceforge.net/apps/trac/sourceforge/wiki/News
|
2009-10-30 18:54:42 +01:00
|
|
|
|
