Version 5 (modified by exarkun, 10 years ago) (diff)


  1. See admin/release-procedure.txt
  2. Put the release tarball in the appropriate subdirectory of /twisted/Releases/
  3. Edit the wiki page for the released project
    1. Add a new section for current stable release
      1. Put new version number in visible text
      2. Point the download link at the new download URL on tmrc
    2. Delete any existing old stable release
    3. Relabel the old stable release as the old stable release
    4. Point the release notes at the trac browser URL for NEWS file in the release tag (if the release is Twisted, point to all of the NEWS files for all included subprojects)
  4. Update the documentation
    1. Create a ticket
    2. Create a branch of WebSite
    3. Switch to the branch
    4. Update website documentation
    5. Delete old doc directory
    6. Commit
    7. Copy doc out of release tarball into WebSite WC in place of old doc directory
    8. svn add
    9. commit
    10. Generate new book.pdf with admin/process-docs and put it in the branch in the right place. Do not be afraid of the output of process-docs.
    11. Follow rest of normal UQDS with the following additions:
      1. Bring up staging server on alternate ports on pyramid
        1. More detail here
      2. Make sure the links are correct, the text is properly processed, etc
  5. Update the wiki front page with new version number and download links
  6. Send out release announcement
    1. twisted-python@…
    2. python-announce@…
    3. freshmeat
    4. Update front page of

Here is some Crap that I will paste on to the page.

radix@takkun ~/Projects/WebSite/branches/docs-2.4-1749/vhosts/ for x in conch core lore mail names web words; do  
cp -r Twisted-2.4.0/Twisted`python -c 'import sys; print sys.argv[1].title()' $x`*/doc/* $x/documentation/
svn add $x/documentation/*

Was that good