Move release process document to version control

[jml]

ReleaseProcess should be moved into version control and managed there.

The document on the wiki is now basically complete and probably mostly accurate. Where it's wrong, that's a defect, and where the process can be changed to be better, that's an enhancement.

The length and complexity of the process it describes makes it a near essential to doing the release. It ought to live near all of the other release essentials.

It refers to numerous scripts based in the tree. When these scripts change, the document ought to change as well.

[glyph]

If the sphinx conversion is imminent, it might be worthwhile to wait for it. However, sphinx or lore, how do you propose to convert the document into something suitable for viewing and editing in SVN as opposed to trac markup? (Are you volunteering to do the translation manually?)

[jml]

Yes, volunteering to do the transition manually.

Where can I track progress on Sphinx stuff?

Note that switching to Sphinx rather than Lore requires changes to the release process itself, which is one of the reasons I'm keen to have this in the tree.

[glyph]

Replying to jml:

Yes, volunteering to do the transition manually. Where can I track progress on Sphinx stuff?

The best answer I can find is this:  http://twistedsphinx.funsize.net/transition_plan.html

Somebody should really bug khorn to turn that into a ticket.

Note that switching to Sphinx rather than Lore requires changes to the release process itself, which is one of the reasons I'm keen to have this in the tree.

Yes, definitely.

[jml]

I've filed #4553 to be that master ticket.

[thijs]

Replying to jml:

I've filed #4553 to be that master ticket.

See #4500 for the master ticket.