Tree Closing Window Execution#

The checklist below is for before, during, and after a Tree Closing Window (TCW). These are the actions for almost any TCW. Most will benefit from specific additions.

Wednesday Before#

Review any notes or bugs from prior TCWs that may be relevant.

Ensure the decision on “hard close” vs. “soft close” has been made.

Make sure all communications have gone out from the Planning Procedure.

Double check all bugs to be included, make sure you know how to recover from potential issues. The CAB list is the “source of truth”.

Day of TCW#

Check and screenshot various dashboards to see what is current “normal”.

(optional) post message in IRC channels in advance. Usually #mobile, #developers, and #releng. Sample:

REMINDER - Trees close in about 1 hour for

Pull up local copies of all bugs and the spreadsheet, in case of network issues (planned, or unplanned)

Log in to the primary and backup IRC channels, see IT IRC usage, make sure you have latest passwords.

Touch base with the MOC “on duty” person about 15 minutes before scheduled start of TCW.

Close the trees with the tracker bug URL mentioned. (For “soft tree closing” TCW:

  • Hard close autoland first.

  • Select all the open branches and add the message “TCW in process, devs need to handle their own restarts”, and “open” them saving state.

When TCW Done, Before Opening Trees#

Check nagios dashboard that all is as expected.

Check build API for pending, running, and recent to ensure those system are up.

Check Treeherder to ensure it is up.

Reopen regular trees.

Reopen autoland (if closed for this TCW).

Update notes and file bugs as appropriate to capture any issues. Invite all TCW participants to do the same.

Next Business Day#

Review any notes or bugs, and ensure they have enough context.

File Bugzilla tickets for any work that must be done. Put a link to the Bugzilla ticket in the GitHub issue, but do not close the issue until the bug is fixed.