Confirmed users
1,094
edits
Media/WebRTC: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Sescalante (talk | contribs) |
Sescalante (talk | contribs) No edit summary |
||
| Line 119: | Line 119: | ||
*[[Media/WebRTC/2012-04-26| Meeting Notes from Thu, Apr 26, 2012]] | *[[Media/WebRTC/2012-04-26| Meeting Notes from Thu, Apr 26, 2012]] | ||
*[[Media/WebRTC/2012-04-19| Meeting Notes from Thu, Apr 19, 2012]] | *[[Media/WebRTC/2012-04-19| Meeting Notes from Thu, Apr 19, 2012]] | ||
==Bugzilla Flags (in review)== | |||
By using the following whiteboard text and Bugzilla flags for tracking User Stories, Estimates, Target Milestones, and Blocked; we'll produce reports on how much work we have per sprint, how likely we'll land that work, and determine risks early. | |||
'''Task Bugs: Estimates''' | |||
* Estimates go on the dependent bugs, not [meta] bugs | |||
* Except: new meta bugs that don't have any dependent bugs yet | |||
* Grammar: [p={estimate}] | |||
* The entire block is contained within square brackets, along with other tags | |||
* Case-insensitive. p and P are both valid. | |||
* Key and value are separated by a equal sign (no spaces). | |||
* Key/value pairs are separated by a space and comma. | |||
* Example: [p=5, ft:systems-fe] | |||
* Initial may be filled in after a bug scrub with Engineering Leads | |||
* On-going maintenance by developers, who know when information changes | |||
'''Task Bugs: Target Milestones''' | |||
* Target milestone set for [meta] and dependent bugs landing milestone | |||
* [meta] bugs are set for milestone when last dependent bug is fixed | |||
* On-going maintenance by developers, discussion with team on impact when milestone changes | |||
'''Task Bugs: Blocking''' | |||
* Blocking Bugs will set Project Flag to: {release}+ | |||
* Blocking Bug Nominations will set Project Flag to: {release}? | |||
'''User Story Data''' | |||
* ONE bug per user story, starting with the word [meta] | |||
* Implementation tasks and bugs should be marked as blocking the user story bug. | |||
* The user story id, as found in the Product backlog spreadsheet, is written in the bug whiteboard as "ucid:{id}", eg: "ucid:Browser326". | |||
* The user story priority for a release is either P1 (committed) or P2 (targeted). This is written in the bug whiteboard as "{release}:{priority}", eg: "1.3:P1". | |||
* The functional team that is responsible for the implementation of the user story is written as "ft:{teamname}", eg: "ft:media". | |||
'''User Story Format''' | |||
* Grammar: [ucid:{id}, {release}:p{1,2}, ft:{team-id}] | |||
* The entire block is contained within square brackets | |||
* Case-insensitive. UCID and ucid are both valid. | |||
* Key and value are separated by a colon (no spaces). | |||
* Key/value pairs are separated by a space and comma. | |||
* Example: [ucid:System26, 1.3:P2, ft:systems-fe] | |||