Auto-tools/Projects/Mozmill/Release

Releasing Mozmill has a lot of moving parts. Here's how it's done.

Releasing a Preview Release (aka Release to PyPi)

For previews (beta, alpha, rc etc) it's pretty easy. You just send it up to pypi because bothering the AMO Editors for review of a pre-release addon really wastes their time. The one exception to this is for major releases, it might be good to get AMO editor feedback early. But in general, for these releases, we just go to pypi. It's done like so:

1. Bump your version: git checkout -b versionbump (do this from your dev branch for the release) 2. Change all the setup.py/install.rdf's to have the proper <blah>rcX version where X is your rc number. For betas, use 'beta' etc. Pretty straightforward. 3. Make a bug and attach the patch from 2 for review. This is a good step just to ensure we don't miss anything. Leave that bug open until we release so that you don't have to have a new bug for every silly version bump (i.e. rc1, then rc2 etc) 4. Once you have review commit your change to the development branch 5. Go into each directory (mozrunner/mozmill/jsbridge) and issue the following command: python setup.py sdist upload

Note: For step 5, you'll have to have a key registered with pypi and be listed as a maintainer of the pypi packages in order for the upload step to work. If you need that access for some reason, let harth or ctalbert know.