2009-10-30 18:54:42 +01:00
|
|
|
How to release a new version of SemanticScuttle
|
|
|
|
|
===============================================
|
|
|
|
|
|
|
|
|
|
0. Run unit tests and verify that all of them pass
|
2011-07-21 22:28:42 +02:00
|
|
|
1. Update ``doc/ChangeLog``
|
|
|
|
|
2. Update ``doc/UPGRADE.txt``
|
2011-08-01 21:53:00 +02:00
|
|
|
3. Update version in ``data/templates/default/about.tpl.php``,
|
2011-07-21 22:28:42 +02:00
|
|
|
``build.xml`` and ``doc/README.rst``
|
2010-06-09 08:05:48 +02:00
|
|
|
4. Create a release zip file via the build script:
|
2011-07-21 22:28:42 +02:00
|
|
|
Just type "``phing``".
|
2010-06-09 08:05:48 +02:00
|
|
|
5. Make a test installation from your zip file with a fresh
|
2009-11-14 11:24:08 +01:00
|
|
|
database. Register a user, add bookmarks etc.
|
2010-06-09 08:05:48 +02:00
|
|
|
6. When all is fine, it's time to release.
|
2009-11-14 11:24:08 +01:00
|
|
|
The build script takes care for most of the
|
|
|
|
|
tasks.
|
2011-07-21 22:28:42 +02:00
|
|
|
Run "``phing release``", and it will upload the release to
|
2011-08-08 08:12:20 +02:00
|
|
|
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/
|
