RELEASING TWISTED CORE OR A SUBPROJECT
- Fix all release-critical bugs in http://twistedmatrix.com/bugs/
- Verify that the supported platforms on buildbot ( http://buildbot.twistedmatrix.com/supported ) are ALL GREEN.
- Create a ticket for releasing your project at http://twistedmatrix.com/bugs/.
- mkbranch Twisted releases/twisted-<projname>-<a.b>.x-<ticketnumber> # The last 'x' in the version number is literal.
- Write release notes in proj/topfiles/NEWS, including a date and a version number.
- 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.
- Add a Quote of the Release to [source:trunk/twisted/topfiles/README twisted/topfiles/README] if you are releasing Twisted Core.
- Run the release script: ./admin/[source:trunk/admin/release-twisted release-twisted] --commands=exportTemp,makeDocProj,makeBallProj
- Test the produced tarballs. Install them, run tests, etc.
- svn commit
- 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>
- Merge the branch to trunk.
- Distribute, announce, and so forth.
RELEASING TWISTED SUMO
- From Twisted trunk WC, mkdir twistedballs.
- Put all current subproject tarballs into twistedballs. Just copy unchanged projects from the previous Twisted tarball.
- Put ZopeInterface-*.tgz in twistedballs.
- ./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.
- ./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.
- Commit the changed README file to trunk, author: release-twisted, reviewer: you.
- Distribute, announce, etc.
CREATING A NEW SUBPROJECT
- 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.
- mkdir twisted/<proj>/topfiles
- Create a setup.py, copying/modifying from e.g. [source:/trunk/twisted/conch/topfiles/setup.py twisted/conch/topfiles/setup.py].
- If your project has extension modules, see [source:trunk/twisted/runner/topfiles/setup.py twisted/runner/topfiles/setup.py] as an example.
OK SOME OTHER STUFF
- Put the release tarball in the appropriate subdirectory of /twisted/Releases/
- Edit the wiki page for the released project
- Add a new section for current stable release
- Put new version number in visible text
- Point the download link at the new download URL on tmrc
- Delete any existing old stable release
- Relabel the old stable release as the old stable release
- 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)
- Update the documentation
- Update website documentation
- 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.
- Read vhosts/twistedmatrix.com/projects/place.py and pray.
- Update the wiki front page with new version number and download links
- Send out release announcement
- Update front page of twistedmatrix.com.
Download in other formats: