[Zope3-dev] Automated egg releases

[Marius Gedminas]

People make mistakes.  Can we reduce the number/severity of those
mistakes by creating a Python script to automate the release process as
much as possible?  Things like:

  - check that the version number in setup.py doesn't match an existing
    release in cheeseshop

  - check whether you have modified but not committed (or unversioned)
    files in the source tree

  - check that you've created a tag in subversion for this release (or,
    alternatively, offer to create the tag for you)

  - build an egg, install it locally in a temporary directory, then run
    the test suite to check for any missing files or whatever

        (a somewhat related idea would be to set up a buildbot to check
        for new zope-related egg releases and run their test suite in a
        sandbox, to notice breakages and email the guilty parties)

  - run the correct setup.py command to build/register/upload the egg to
    cheeseshop and/or www.zope.org

I'd be happy to work on such a script during the sprint, if someone
could help me figure out what exactly it should to do.

Marius Gedminas
-- 
If something has not yet gone wrong then it would ultimately have been
beneficial for it to go wrong.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://mail.zope.org/pipermail/zope3-dev/attachments/20070926/8efcdd9b/attachment-0001.bin