summaryrefslogtreecommitdiff
path: root/doc/developers/release-new-version.rst
blob: de2c4e33659e1475ba5acc3d49a8dbacda761722 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
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/default/about.tpl.php``,
   ``build.xml`` and ``doc/README.rst``
4. Create a release zip file via the build script:
   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
   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/