Update release automation to work with recent version changes

[radix]

For example, admin/change-versions.

[radix]

Ok, work has started in release-versioning-1668. I've gotten rid of the redundancy of version in setup.py files, by moving version specification into _version.py files in each project directory.

Things left to do:

• Figure out why subproject versions aren't getting revision numbers
• Change change-versions so that it replaces old version with new version in README files, instead of replacing "SVN-Trunk" etc with new-version.

[radix]

The first poin is fixed and the second point I'm ignoring : trunk will just contain README files with the "replace-me" tags instead of actual version numbers. Real version numbers will still be available in python code.

[radix]

Sorry, I don't know how this got assigned to glyph.

[radix]

review! source:/branches/release-versioning-1668.

[Jean-Paul Calderone]

• twisted/python/dist.py - getVersion should have a docstring
• admin/change-versions
  • most of this code should be in twisted/python/ somewhere (dist.py, I guess). The script should import main from there and call it and not much else.
  • loadVersionFrom should have a unit test and docstring
  • replaceProjectVersion should have a unit test and a docstring

[radix]

all issues addressed. Please re-review.

[Jean-Paul Calderone]

There are still a couple occurances of "twisted" in getVersion that should be base instead.

verstringMatcher should use a raw string, even though r"\." == "\."

Add whitespace around assignments near the end of inputNewVersion

Everything else looks cool.

[radix]

I've fixed these issues and merged in r16792.