Changes between Version 16 and Version 17 of ReleaseProcedure


Ignore:
Timestamp:
02/24/2011 10:51:34 AM (3 years ago)
Author:
jknight
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v16 v17  
    1  
    2 This page is super out-of-date and completely wrong. See ReleaseProcess for the new version. 
    3  
    4 = RELEASING TWISTED CORE OR A SUBPROJECT = 
    5  
    6  1. Fix all release-critical bugs in http://twistedmatrix.com/bugs/ 
    7  1. Verify that the supported platforms on buildbot ( http://buildbot.twistedmatrix.com/supported ) are ALL GREEN. 
    8  1. Create a ticket for releasing your project at http://twistedmatrix.com/bugs/. 
    9  1. {{{mkbranch Twisted releases/twisted-<projname>-<a.b>.x-<ticketnumber> # The last 'x' in the version number is literal.}}} 
    10  1. Write release notes in {{{proj/topfiles/NEWS}}}, including a date and a version number. 
    11  1. Run ./admin/[source:trunk/admin/change-versions change-versions]. Specify the versions of whatever you're releasing. Core should be versioned as release.major.minor, where minors are only bugfixes, majors are functionality increases, and releases are major milestones. 
    12  1. Add a Quote of the Release to [source:trunk/twisted/topfiles/README twisted/topfiles/README] if you are releasing Twisted Core. 
    13  1. Run the release script: ./admin/[source:trunk/admin/release-twisted release-twisted] --commands=exportTemp,makeDocProj,makeBallProj 
    14  1. Test the produced tarballs. Install them, run tests, etc. 
    15  1. {{{svn commit}}} 
    16  1. Tag the release. {{{svn cp -m 'Tagging for Twisted <proj> <a.b.c> release' $TREPO/branches/releases/twisted-<proj>-<a.b>.x-<ticketnumber> $TREPO/tags/releases/twisted-<proj>-<a.b.c>}}} 
    17  1. Merge the branch to trunk. 
    18  1. Distribute, announce, and so forth. 
    19  
    20 = RELEASING TWISTED SUMO = 
    21  
    22  1. From Twisted trunk WC, {{{mkdir twistedballs}}}. 
    23  1. Put all current subproject tarballs into twistedballs. Just copy unchanged projects from the previous Twisted tarball. 
    24  1. Put {{{ZopeInterface-*.tgz}}} in twistedballs. 
    25  1. ./admin/[source:trunk/admin/change-versions change-versions] --sumo-only, and make sure all the versions are appropriately specified for the tarballs you've included. Eventually it shouldn't be necessary to change any version but the Twisted one. 
    26  1. ./admin/[source:trunk/admin/release-twisted release-twisted] --commands=makeBallSumo --sumo-version=a.b.x.y' where 'a.b.x' is the version of Twisted Core contained in this release (see point 6 in "Releasing Core or a Subproject" above), and 'y' is simply a monotonically increasing nonnegative integer as long as 'a.b.x' is the same as the last release. 
    27  1. Commit the changed {{{README}}} file to trunk, author: release-twisted, reviewer: you. 
    28  1. Distribute, announce, etc. 
    29  
    30 = CREATING A NEW SUBPROJECT = 
    31  
    32  1. Add the project name to [source:/trunk/twisted/python/dist.py twisted/python/dist.py]'s list of subprojects and [source:/trunk/setup.py setup.py]'s list of subprojects. 
    33  1. {{{mkdir twisted/<proj>/topfiles}}} 
    34  1. Create a {{{setup.py}}}, copying/modifying from e.g. [source:/trunk/twisted/conch/topfiles/setup.py twisted/conch/topfiles/setup.py]. 
    35  1. If your project has extension modules, see [source:trunk/twisted/runner/topfiles/setup.py twisted/runner/topfiles/setup.py] as an example. 
    36  
    37 = OK SOME OTHER STUFF = 
    38  
    39   1. Put the release tarball in the appropriate subdirectory of /twisted/Releases/ 
    40   1. Edit the wiki page for the released project 
    41     1. Add a new section for current stable release 
    42       1. Put new version number in visible text 
    43       1. Point the download link at the new download URL on tmrc 
    44     1. Delete any existing old stable release 
    45     1. Relabel the old stable release as the old stable release 
    46     1. 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) 
    47   1. Update the documentation 
    48     1. [wiki:APIDocs Update website documentation] 
    49     1. Generate new {{{book.pdf}}} with [source:trunk/admin/process-docs admin/process-docs] and put it in the branch in the right place.  Do not be afraid of the output of {{{process-docs}}}. 
    50     1. Read vhosts/twistedmatrix.com/projects/place.py and pray. 
    51   1. Update the wiki front page with new version number and download links 
    52   1. Send out release announcement 
    53     1. twisted-python@twistedmatrix.com 
    54     1. python-announce@python.org 
    55     1. freshmeat 
    56     1. Update front page of twistedmatrix.com. 
    57   1. Update ReleaseRevisions with information for the new release 
     1See ReleaseProcess.