Runway/Queue: Difference between revisions
< Runway
Jump to navigation
Jump to search
No edit summary |
|||
| Line 4: | Line 4: | ||
Add your bugs here to have them scheduled for landing on the [[Runway|runway]]. Be sure to ping the [[Sheriff_Schedule|sheriff on duty]] to let them know once you've added your entry to the list. | Add your bugs here to have them scheduled for landing on the [[Runway|runway]]. Be sure to ping the [[Sheriff_Schedule|sheriff on duty]] to let them know once you've added your entry to the list. | ||
'''How to add to the queue''' | |||
* use {{bug|#}} to add your bug | |||
* the pilot must be around to check in the code and help it land | |||
* include a summary so the sheriff can prioritize | |||
* include the pilot's availability | |||
{|cellpadding="3" | {|cellpadding="3" | ||
Revision as of 17:13, 10 May 2006
The runway is used to control landings on the trunk in order to ensure that patches have no significant deleterious effect on the tree. The runway is under complete control of the sheriff.
Runway Queue
Add your bugs here to have them scheduled for landing on the runway. Be sure to ping the sheriff on duty to let them know once you've added your entry to the list.
How to add to the queue
- use bug # to add your bug
- the pilot must be around to check in the code and help it land
- include a summary so the sheriff can prioritize
- include the pilot's availability
| Bug | Pilot | Summary | requested time |
| bug 10001 | bz | Ts regression fix, pretty scary! | afternoons PDT |
| bug 10002 | Enn | WHATWG storage piece, Ts impact expected | afternoons EDT |