DevTools/Planning/Status

Force Page Refresh

All work in DevTools should be tied to feature tracking bugs and assigned the right whiteboard flags to reflect the status of each feature bucket. Development managers are responsible to create the dependencies (blocks) for all bugs that tie to a particular feature bucket. We are not following any "user story" methodology for requirements, but we do want to track what the requirements are in the user story field. Even a vague summary is fine. This field is editable and mutable over time.

For individual team status pages, please refer to the following pages:

Paris (Paul Rouget's team): DevTools/Planning/Status/Paris
London: (Joe Walker's team): DevTools/Planning/Status/London
Toronto: (Rob Campbell's team): DevTools/Planning/Status/Toronto
Los Angeles: (Dave Townsend's team): DevTools/Planning/Status/LosAngeles

Bucket Statuses

Whiteboard tags represent the following:

[status:backlog] = this is in the backlog as an idea being considered to add to the pipeline of work.
[status:planned] = planning to work on this within the next 90 days, requirements and design still being refined.
[status:inflight] = this feature is in flight and being worked on.
[status:landedoff] = this feature has landed in nightly with pref off.
[status:landedon] = this feature has landed in nightly with pref on.
[status:shipped] = this feature is completed and shipping.
[status:onhold] = work has been put on hold because of other higher priorities.