Changes between Version 10 and Version 11 of CommitterCheckList


Ignore:
Timestamp:
06/13/2013 06:12:12 PM (19 months ago)
Author:
tom.prince
Comment:

Point to twisted-dev-tools.

Legend:

Unmodified
Added
Removed
Modified
  • CommitterCheckList

    v10 v11  
    3434      1. Explain what broke and how and perhaps on which platform in the commit message 
    3535  1. If you are merging a branch into trunk, you must commit exactly the merge.  You may not make extra changes in the trunk working copy after the merge. 
    36   1.  Use [http://bazaar.launchpad.net/~twisted-dev/twisted-trac-integration/trunk/view/head:/tools/force-builds.py force-builds.py] if you want to test a branch on all supported builders before merging 
     36  1.  Use `force-build` if you want to test a branch on all supported builders before merging 
    3737    1. No, really, use it.  It saves a lot of time. 
    38     1. `bzr branch lp:twisted-trac-integration` to get the trac integration repository - `force-builds.py` is in the subdirectory `tools` 
    39     1. `force-builds.py` prints a link to a results page; mention it in the ticket as a link with the text "Build results" like this: `[url-goes-here Build Results]` 
     38    1. `pip install twisted-dev-tools` to get `force-build` and other useful tools. 
     39    1. `force-build` prints a link to a results page. The build results are also linked from the ticket page. 
    4040    1. There are certain unit-tests on certain builders that are known to fail intermittently. There's no official list of such tests, but you can look at [http://buildbot.twistedmatrix.com/boxes-supported?branch=trunk&num_builds=20 the history of trunk builds] for a particular builder to see if a particular failure shows up a lot. If you're sure that a given build failure is intermittent and not caused by the changes in your branch, you can still merge. 
    4141    1. See UsingBuildbot for more help.