Move release process document to version control
|Reported by:||Jonathan Lange||Owned by:||hawkowl|
|Priority:||normal||Milestone:||totally automated release infrastructure|
|Cc:||Thijs Triemstra, Trevor Bramwell||Branch:||
branch-diff, diff-cov, branch-cov, buildbot
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.
Change History (15)
comment:8 Changed 3 years ago by
|Cc:||Trevor Bramwell added|
|Owner:||Trevor Bramwell deleted|
|Status:||assigned → new|
comment:9 Changed 3 years ago by
|Status:||new → closed|
comment:13 Changed 12 months ago by
|Owner:||set to hawkowl|
|Status:||reopened → new|