## Leading up To Release

1. develop software test-first, test
2. release package to directory, test
3. Deploy as a release candidate on knowledgeforge.net/test.kforgeproject.com

## Release

(dm + kforge)

1. Write a release notice
  * Including changelog (update CHANGES)
2. Tag release in subversion
  * make necessary changes to tag (or do first in trunk) such as setting
    version number
3. Deploy release
  1. cheeseshop: python setup.py egg_info -RDb "" sdist bdist_egg register upload
  2. test.kforgeproject.com: Build tar.gz file and upload to kforgeproject.com
    * upload download page on test.kforgeproject.com
4. Post about release
  1. Freshmeat
  2. kforgeproject.com
  3. blog.okfn.org
 

### Subversion tagging

svn cp url -> url

e.g.

svn cp https://knowledgeforge.net/kforge/svn/trunk https://knowledgeforge.net/kforge/svn/tags/kforge-0.13

### Release Notice Template

KForge 0.13 is out. Get it via the download page:

  <http://www.kforgeproject.com/download/>

Or direct from

  <http://www.kforgeproject.com/files/kforge-0.13.tar.gz>

#### Changes

${insert_changes_here}

#### About KForge ####

KForge is an open-source (GPL) system for managing software and knowledge projects. It re-uses existing best-of-breed tools such as a versioned storage (subversion), a tracker (trac), and wiki (trac or moinmoin), integrating them with the system's own facilities (projects, users, permissions etc). KForge also provides a complete web interface for project administration as well a fully-developed plugin system so that new services and features can be easily added.

For more information see the about page: <http://www.kforgeproject.com/about/>