Firefox OS/ProgramManagement: Difference between revisions
Jump to navigation
Jump to search
| Line 47: | Line 47: | ||
'''Data''' | '''Data''' | ||
* 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 id, as found in the Product backlog spreadsheet, is written in the bug whiteboard as "ucid:{id}", eg: "ucid:Browser326". | ||
* The functional team that is responsible for the implementation of the user story is written as "ft:{teamname}", eg: "ft:media". | * The functional team that is responsible for the implementation of the user story is written as "ft:{teamname}", eg: "ft:media". | ||
'''Format''' | '''Format''' | ||
* Grammar: [ucid:{id}, {release | * Grammar: [ucid:{id}, {release-version}, ft:{team-id}] | ||
* The entire block is contained within square brackets | * The entire block is contained within square brackets | ||
* Case-insensitive. UCID and ucid are both valid. | * Case-insensitive. UCID and ucid are both valid. | ||
| Line 58: | Line 57: | ||
'''Examples''' | '''Examples''' | ||
* [ucid:System26, 1.3 | * [ucid:System26, 1.3, ft:systems-fe] | ||
* [ucid:Comms27, 1.3 | * [ucid:Comms27, 1.3, ft:comms] | ||
Revision as of 02:43, 29 April 2014
Who
- Candice Serran
- Michael Treese
- Kevin Hu
- Joe Cheng
- Ivan Tsay
- Wesley Huang
- Howie Chang
How
TODO: fill in details below
- Description of functional teams goes here
- Description Bugzilla process goes here
- Communication
- List the mailing lists
- List the weekly reports and sprint reports, etc
Functional Teams
Function team details: FirefoxOS/functionalteams
- Productivity
- Media
- Performance
- Browser
- Comms (Dialer, SMS, Contacts)
- Systems (Notification, Apps Install, Customizations)
- System Platform (Keyboard, Settings, Lockscreen)
- Multi-media platform (Audio/Video Encoding)
- WebRTC (Audio/Video P2P connections, Get User media (gUM))
- RIL (Telephony, Network)
- GFX, Layout, Audio
- Devices
Bugzilla Flags
The team will be using the following whiteboard text for tracking user stories and their priorities in Bugzilla.
Overview
- ONE bug per user story. Implementation tasks and bugs should be marked as blocking the user story bug.
- ALL user stories that are either committed or targeted to a release must have a bug filed.
- If a bug is not a user story it will NOT have any of these flags in the whiteboard.
Data
- The user story id, as found in the Product backlog spreadsheet, is written in the bug whiteboard as "ucid:{id}", eg: "ucid:Browser326".
- The functional team that is responsible for the implementation of the user story is written as "ft:{teamname}", eg: "ft:media".
Format
- Grammar: [ucid:{id}, {release-version}, 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.
Examples
- [ucid:System26, 1.3, ft:systems-fe]
- [ucid:Comms27, 1.3, ft:comms]