Tree Rules/comm-central/Closing comm-central

From MozillaWiki
Jump to navigation Jump to search

If you have admin access to tinderbox, you can close comm-central.

The comm-* repositories have a hg hook installed in them so that when the tree is closed, they will deny access to the tree unless "CLOSED TREE" is included in the comment for the tip of the changesets being pushed.

Control of the trees

How to close a tree/project

For each tree you wish to close:

  • Go to the Tinderbox page for the tree, at the bottom of the page select "Administrate Tinderbox Trees".
  • In the "Status Message" box, find the line that says:
<p><span id="tree-status">OPEN</span><span id="extended-status"></span>
  • Change OPEN (or whatever it may say) to CLOSED.
    • DO NOT reformat/change/alter any of the rest of the line. If you do you won't have the protection that the hg hooks give you.
  • A little bit lower down, put the reason the tree is closed in the tree reason section, and add a name to the sheriff if necessary:
var treeReason = "I wanted to";
 var treeSheriff = 'annoyingPerson on <a href="irc://irc.mozilla.org/maildev">#maildev</a>';
  • Update the tree status on the irc channel if necessary.

Opening the tree

  • Reverse the closure steps, don't forget to clear the treeReason and just the name of the treeSheriff (leave the treeSheriff pointing to an irc channel as that will be displayed when the tree is busted or orange).
  • For comm-1.9.1 based trees, please leave the status as "RESTRICTED" (rather than OPEN) as these trees require approvals for checkins.

Areas of Closure

Projects

If the tree is closed for one project, the hg hook will automatically allow changes through for other projects as long as they don't affect the closed one.

The tree is split up as follows:

  • SeaMonkey directories: suite
  • Calendar directories: calendar, other-licenses/branding/sunbird
  • Thunderbird: all other files and directories.

Branches

The following repositories are affected by the status on the following trees:

The status on Thunderbird3.1 doesn't currently affect anything as we haven't branched comm-central into comm-1.9.2 yet.