something like:

if pass tests:
bzr export blah.tar.gz

I don't think you can upload directly to redmine from a shell (I tried and couldn't figure it out).

We should probably have our release script create a branch for each release that we can publish nightlies of. This allows us to port back patches.

For instance, I really want 1.X to have spacepoints. But third_party issues should port back to the 0.X series.

How we tie it in with redmine is unclear. Maybe we should just put everything here:

http://micewww.pp.rl.ac.uk/static_files/

instead?

Let's say 0.7 (preparing for 1.0 release candidate) if that's okay since you asked about putting out antoher dot release.

I did this:

1. Check jenkins that the trunk latest commit and fresh builds work.
2. bzr tag MAUS-v0.X
3. bzr export maus-v0.X.tar.gz
4. Go to files section and upload

Thinking on the fly: do we want to hold back stuff at this step from releases? Somehow add a file called ".COMPONENT_RELEASE_STATUS" which can mean that code doesn't go into the release or something?

Okay for alpha release I guess. I wanted to figure out some documentation stuff as well.

Also we should be making release notes.

Another thing for the list: update release notes and changelog.