diff options
Diffstat (limited to 'doc/developers/release-new-version.rst')
| -rw-r--r-- | doc/developers/release-new-version.rst | 23 |
1 files changed, 16 insertions, 7 deletions
diff --git a/doc/developers/release-new-version.rst b/doc/developers/release-new-version.rst index a5e77dc..de2c4e3 100644 --- a/doc/developers/release-new-version.rst +++ b/doc/developers/release-new-version.rst @@ -4,7 +4,7 @@ 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``, +3. Update version in ``data/templates/default/about.tpl.php``, ``build.xml`` and ``doc/README.rst`` 4. Create a release zip file via the build script: Just type "``phing``". @@ -14,9 +14,18 @@ How to release a new version of SemanticScuttle 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 - + sourceforge. +7. Create a git tag and push it +8. Create the PEAR package and test it: + Run ``phing package``, then + ``pear upgrade dist/pear/SemanticScuttle-0.xx.tgz`` +9. Publish the PEAR package: ``phing deploy-sf-pear`` +10. Publish the documentation: ``phing deploy-docs`` +11. Write announcement mail to the SemanticScuttle mailing list + semanticscuttle-devel@lists.sourceforge.net +12. Announce the new release in the sourceforge project news + https://sourceforge.net/news/submit.php?group_id=211356 + Help about the process is available in + https://sourceforge.net/apps/trac/sourceforge/wiki/News +13. Set the default file in + https://sourceforge.net/projects/semanticscuttle/files/SemanticScuttle/ |