Opened 4 years ago

Closed 6 months ago

#4543 task closed wontfix (wontfix)

Move release process document to version control

Reported by: jml Owned by:
Priority: normal Milestone: totally automated release infrastructure
Component: release management Keywords: documentation
Cc: thijs, trevor@… Branch:
Author: Launchpad Bug:

Description

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.

Attachments (1)

version-control-release-process-4543-1.patch (20.4 KB) - added by bramwelt 6 months ago.
ReST Version of Release Process

Download all attachments as: .zip

Change History (10)

comment:1 Changed 4 years ago by 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?)

comment:2 follow-up: Changed 4 years ago by 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.

comment:3 in reply to: ↑ 2 Changed 4 years ago by 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.

comment:4 follow-up: Changed 4 years ago by jml

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

comment:5 Changed 4 years ago by <automation>

  • Owner radix deleted

comment:6 in reply to: ↑ 4 Changed 4 years ago by thijs

  • Cc thijs added

Replying to jml:

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

See #4500 for the master ticket.

comment:7 Changed 6 months ago by bramwelt

  • Owner set to bramwelt
  • Status changed from new to assigned

Changed 6 months ago by bramwelt

ReST Version of Release Process

comment:8 Changed 6 months ago by bramwelt

  • Cc trevor@… added
  • Keywords review added
  • Owner bramwelt deleted
  • Status changed from assigned to new

I have manually converted (with a little help from html2rst) the Release Process wiki page into reStructuredText format.

None of the content should have changed, though it is probably in the process I might have munged some text while updating the formatting.

The initial text regarding changes to the doc I placed in a 'warning' declaration, and any obvious notes I replaced with note declarations.

comment:9 Changed 6 months ago by exarkun

  • Keywords review removed
  • Resolution set to wontfix
  • Status changed from new to closed

Considering the release process is still changing, mostly in response to surprises encountered by release managers, and that there are currently known problems with the process, I think that it would be premature to make this change.

In fact, I wonder why we want to do it at all. The ticket description says "It ought to live near all of the other release essentials." but this doesn't sound like much of a reason. It's not hard to find the ReleaseProcess wiki page. It *is* kind of hard to find most of the rest of our documentation though...

Note: See TracTickets for help on using tickets.