release workflow

0. ensure that tests pass

both on travis and locally:

./setup.py test

1. update NEWS file.

It should list only user-relevant changes.

2. bump version

vim alot/__init__.py
git commit -m "bump version string" .
git push

3. tag release

git tag -s 0.8 -m "tag v0.8"      
git push --tags

4. make release on github

Go to https://github.com/pazz/alot/releases/new

• use existing tag 0.8 as base
• use "v0.8" as name
• description = topmost entry from the NEWS file here.

5. sign release files

mkdir tmp && cd tmp
wget https://github.com/pazz/alot/archive/0.8.zip
gpg --armor --detach-sign --local-user patricktotzke 0.8.zip
wget https://github.com/pazz/alot/archive/0.8.tar.gz
gpg --armor --detach-sign --local-user patricktotzke 0.8.tar.gz

Then go to https://github.com/pazz/alot/releases again and attach the *.asc files to the release.

6. send release mail

A rough template follows below.

Subject: [alot] announcing v0.8
To: [email protected]

Hi everyone!

I have just tagged alot v0.8; You can get a tarball here [0].

SUMMARY OF CHANGES
NEWS entry

As usual, a quick hall of fame of recent contributors:
$ git shortlog -s -n 0.7...

New bug reports, feature or pull requests via the projects github page [1]
are always welcome.

Cheers,
P

[0]: https://github.com/pazz/alot/tarball/0.8
[1]: https://github.com/pazz/alot