diff options
| author | Christian Weiske <cweiske@cweiske.de> | 2011-08-08 08:12:20 +0200 |
|---|---|---|
| committer | Christian Weiske <cweiske@cweiske.de> | 2011-08-08 08:12:20 +0200 |
| commit | 062fe09d43b25db5f4790c5ac33ab7e2e9f3b68e (patch) | |
| tree | 930fab6d60bedaa7a51a9c3eb1088b78e715a659 | |
| parent | 4c9560cf67a97f99078d50475a6463037599e117 (diff) | |
| download | semanticscuttle-062fe09d43b25db5f4790c5ac33ab7e2e9f3b68e.tar.gz semanticscuttle-062fe09d43b25db5f4790c5ac33ab7e2e9f3b68e.tar.bz2 | |
update release howto
| -rw-r--r-- | doc/developers/release-new-version.rst | 21 |
1 files changed, 15 insertions, 6 deletions
diff --git a/doc/developers/release-new-version.rst b/doc/developers/release-new-version.rst index 74f4bbd..de2c4e3 100644 --- a/doc/developers/release-new-version.rst +++ b/doc/developers/release-new-version.rst @@ -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/ |