Holistic release automation tool

[radix]

We need a single button that can do the entire release from building to publishing to announcing.

[zooko]

According to radix (on IRC), this ticket is waiting for the following tickets:

#2886, #2888, #2889, #2890, #2891, #2925

[zooko]

According to radix (on IRC), the following are not actually part of the twisted-7.0 milestone as far as he is concerned, but he doesn't mind other people putting crap in there as wishful thinking: #2854, #2307

[zooko]

I guess #2353 -- "Change Twisted "main" release to a time-based version number" -- is relevant. And how about #2308 -- "Test Twisted's release automation" -- ?

[thijs]

Replying to radix:

We need a single button that can do the entire release from building to publishing to announcing.

I'll start working on that button :)

[khorn]

Has anyone here considered using fabric?

 http://fabfile.org

Its designed to do precisely this kind of thing.

[khorn]

Paver might also be a useful tool here:

 http://www.blueskyonmars.com/projects/paver/

[exarkun]

Implicit in this ticket is the requirement for the system to be covered by automated tests to ensure that it continues to work. Do fabfile or paver offer anything in that area?

[khorn]

I'm not aware of anything specific provided by these tools, but as both of them use regular python files to define their "tasks", I would presume you could use standard unit-testing techniques (unittest/trial) to test them. I haven't done anything like this, but I don't see any obvious reason why you couldn't do it.