update upgrade.txt file and ajust changelog
git-svn-id: https://semanticscuttle.svn.sourceforge.net/svnroot/semanticscuttle/trunk@713 b3834d28-1941-0410-a4f8-b48e95affb8f
This commit is contained in:
parent
7333049082
commit
1962e3d2bc
2 changed files with 13 additions and 6 deletions
|
@ -1,6 +1,12 @@
|
|||
Upgrading SemanticScuttle from a previous version
|
||||
=================================================
|
||||
|
||||
|
||||
From version 0.96 to 0.97
|
||||
-------------------------
|
||||
No database changes necessary.
|
||||
|
||||
|
||||
From version 0.95 to 0.96
|
||||
-------------------------
|
||||
Update your database:
|
||||
|
|
|
@ -3,19 +3,20 @@ 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
|
||||
2. Update doc/UPGRADE.txt
|
||||
3. Update version in data/templates/about.tpl.php
|
||||
and build.xml
|
||||
3. Create a release zip file via the build script:
|
||||
4. Create a release zip file via the build script:
|
||||
Just type "phing".
|
||||
4. Make a test installation from your zip file with a fresh
|
||||
5. 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.
|
||||
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.
|
||||
6. Write announcement mail to the SemanticScuttle mailing list
|
||||
7. Write announcement mail to the SemanticScuttle mailing list
|
||||
semanticscuttle-devel@lists.sourceforge.net
|
||||
7. Announce the new release in the sourceforge project news
|
||||
8. Announce the new release in the sourceforge project news
|
||||
https://sourceforge.net/apps/trac/sourceforge/wiki/News
|
||||
|
||||
|
|
Loading…
Reference in a new issue