aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/ChangeLog1
-rw-r--r--doc/developers/release-new-version.rst12
2 files changed, 7 insertions, 6 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog
index 87c1b46..7ed1796 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -26,6 +26,7 @@ ChangeLog for SemantiScuttle
- Support HTTPS connections when ``$root`` is not configured
- SQL schema version table to ease future database upgrades
- Documentation is written with rST (reStructuredText) now
+- Support per-host configuration files
0.97.2 - 2011-02-17
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