diff options
| author | Yalçın Can <ylcncn@gmail.com> | 2011-07-27 14:23:37 +0300 |
|---|---|---|
| committer | Yalçın Can <ylcncn@gmail.com> | 2011-07-27 14:23:37 +0300 |
| commit | efd842174fdd37f8eb2c460c7adb21954bcfbe9d (patch) | |
| tree | a2ab3cc25db92b901b69ce1bc0ad1dedb5d498ef /doc/developers/release-new-version.rst | |
| parent | 8cd40b3d76e191b2fbe95b044f69aed07cc27664 (diff) | |
| parent | 81aa17b8523d95310c90366d9af09767db0c84f2 (diff) | |
| download | semanticscuttle-efd842174fdd37f8eb2c460c7adb21954bcfbe9d.tar.gz semanticscuttle-efd842174fdd37f8eb2c460c7adb21954bcfbe9d.tar.bz2 | |
Merge remote-tracking branch 'upstream/master'
Diffstat (limited to 'doc/developers/release-new-version.rst')
| -rw-r--r-- | doc/developers/release-new-version.rst | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/developers/release-new-version.rst b/doc/developers/release-new-version.rst index 4b2540a..a5e77dc 100644 --- a/doc/developers/release-new-version.rst +++ b/doc/developers/release-new-version.rst @@ -2,18 +2,18 @@ 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 +1. Update ``doc/ChangeLog`` +2. Update ``doc/UPGRADE.txt`` +3. Update version in ``data/templates/about.tpl.php``, + ``build.xml`` and ``doc/README.rst`` 4. Create a release zip file via the build script: - Just type "phing". + 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 + 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 |