jarn.mkrelease (3.5)

Motivation

Here at Jarn, we have switched to zc.buildout and pinned egg versions for customer deployments. This means that for every update, we have to make proper egg releases of all modified packages.

Turns out it's quite a bit of work to put a new egg on a distribution server! After preparing a package for release (update version strings, etc.), we typically have to:

1. Check in modified files.
2. Tag the release in Subversion.
3. Package up an egg.
4. Distribute the egg via scp or upload it to an index server.

Now multiply by the number of packages needing a release, and the moment of I gotta script this approaches at warp 9.

Enter jarn.mkrelease.

Usage

mkrelease[options][svn-url|svn-sandbox]

Options

-C,--skip-checkin

Do not checkin modified files from the sandbox.

-T,--skip-tag

Do not tag the release in subversion.

-S,--skip-scp

Do not scp the release to dist-location.

-D,--dry-run

Dry-run; equivalent to -CTS.

-K,--keep-temp

Keep the temporary build directory.

-s,--sign

Sign the release with GnuPG.

-iidentity,--identity=identity

The GnuPG identity to sign with.

-ddist-location,--dist-location=dist-location

An scp destination specification, or an index server configured in ~/.pypirc, or an alias name for either. This option may be specified more than once.

-h,--help

Print the help message and exit.

-v,--version

Print the version string and exit.

svn-url

A URL with protocol svn, svn+ssh, http, https, or file.

svn-sandbox

A local directory; defaults to the current working directory.