Step-by-Step Instructions
Once all tickets in a milestone have been closed, a new ticket should be created to test the code base. All tests must pass for version to be released. If a test failure occurs and it does not represent a bug in pbooks code, the test must be altered to pass.
Once the tests are passed, that final ticket should be closed.
'''Change version number in pbooks/config/sitemap.xml'''
First create a branch, then make the tag from the branch
Tag /misc_projects/pbooks/apps/pbooks/ and /misc_projects/pbooks/
Package tarball for distribution, calculate md5 and sha256
Create branch for follow-ups?
Branching and Tagging
svn cp file:///home/svn/repos/pbooks/trunk/ file:///home/svn/repos/pbooks/branches/pbooks-0.0x svn cp file:///home/svn/repos/pbooks/branches/pbooks-0.0x file:///home/svn/repos/pbooks/tags/pbooks-0.0x
Packaging, Archiving, and Compressing
cd /home/svn/tagged_checkouts/
svn co file:///home/svn/repos/pbooks/branches/pbooks-0.12
cd pbooks-0.12
find . -name '.svn' -exec rm -rf {} \;
cd ..
tar -cjvf pbooks_portable-0.03.tbz pbooks_portable-0.03/
md5sum pbooks_portable-0.03.tbz
Update and upload package to [http://www.pbooks.org/pub/ PBooks.org downloads].
Should also test the package prior to uploading and releasing. Currently we're only testing the SVN. Test both the update of an existing setup as well as an initial installation.
Trac Administration
Create version which corresponds to release from command line trac-admin.
Trac [/home/trac/pbooks]> version add 0.03 2007-10-22
Use trac web interface to close milestone.
Note to self: write a script to automate this process.