Release procedure

Based on a nice formalization by Glenn Rempe:

1. git pull to get latest code
2. fix the erroring out tests. get clean pass with rake test
3. Update version number in lib/xmpp4r/xmpp4r.rb
4. Add date to CHANGELOG
5. Parse through git log and make sure any big changes are added to CHANGELOG
6. Update the gemspec (critical!) with rake gem:update_gemspec otherwise the gem will not have the current ver num.
7. Replace setup.rb with the newest version
8. git commit and git push those changes
9. Add tag for release with git tag v0.x.x
10. git push --tags
11. clean up/generate the gem and tarball with:
    1. cleanup in prep for gem/tarball generation with rake clobber
    2. generate the gem, tarball and zip files with rake package which puts generated files in pkg/ dir.
    3. Upload files as a new release in RubyForge
    4. Upload files as a new release in gna.org
12. Generate the rdoc files
13. upload the rdoc files to gna.org replacing the existing ones
14. Send announcement to xmpp4r-devel@, possibly jdev@ and ruby-talk@
15. Have a beer