Firefox OS/Comms

Team Backlog

Team back log (including Blockers and Non-blocking backlog)

Priority-wise: Blockers/Regressions > Feature work/Top X > Remaining Bug Backlog

• Dashboard: http://charts.mozilla.org/ffos/blockers.html#responsibility=FxOS_Team&team=Comms
• 1st Priority:
  • 1.3+: http://goo.gl/fetF2x
  • 1.3T+: http://goo.gl/UqA0ZR
  • 1.4+: http://goo.gl/b0sAJF
  • 2.0+: http://goo.gl/OrKrYw
  • 2.0 key focus features: (https://bugzilla.mozilla.org/showdependencytree.cgi?id=985426&hide_resolved=1)
    • feature-b2g=2.0: (http://goo.gl/fWQRkL)
    • user story level: (http://goo.gl/PmbDSW)

• TopX list (http://goo.gl/DSfngu)
  • Smaller chunk of bugs/features that the team can select from if they have no blockers or key focus feature works on their plate. These should have whiteboard tagging as [priority]

• All Non-blocking backlog:
  • blocking-b2g == backlog (http://goo.gl/wxW7fJ)

• Others: without any specific whiteboards
  • Whiteboard with [FT:COMMS] (http://goo.gl/uuGfOO)
    • Tracking those bugs belongs to COMMS team but component are not either DOM: Contacts, Gaia::Contacts, Gaia::Cost Control, Gaia::Dialer, Gaia::SMS, Gaia::Wappush.

To be triaged

• ---:
• 1.3?: http://goo.gl/9bZxCI
• 1.3T?: http://goo.gl/rLxn3Y
• 1.4?: http://goo.gl/Z3TW53
• 2.0?: http://goo.gl/ZizHCO

User stories

User stories: http://goo.gl/fwFdPi

What engineering is working on

To have a bug being considered for attention, just set "blocking-b2g: ?". The triage process will decide if it should block a release or be considered for inclusion in that release.

Contacts

• Features: http://goo.gl/dclgBq
• Blockers: http://goo.gl/pFx8uj
• Sub-team meetings
  • https://wiki.mozilla.org/Gaia/Contacts/Scrum/3
  • Daily irc/etherpad standup ~ 3:30pm Taipei / 9:30am EU
  • Sprint planning on Friday before the team planning

Message

• Features: http://goo.gl/xes5in
• Blockers: http://goo.gl/zTv5UP
• Sub-team meetings
  • https://wiki.mozilla.org/Gaia/SMS/Scrum
  • Daily irc/etherpad standup ~ 3:45pm Taipei / 9:45am EU
  • Sprint planning on Tuesday before the team planning

Dialer

• What are we working on (until June 23 2014)

What we'll we work on next, by order of priority:

1. Blockers
2. Features
3. Nice to have

Sprint planning happens on Mondays at 15h30 Paris/ 9h30 Toronto/ 21h30 Taipei.

Others (Cost control / Wappush)

• Features: http://goo.gl/5j4ORn
• Blockers: http://goo.gl/yvhVWO

For team roles and meeting time, refer to https://etherpad.mozilla.org/comms-subteams

Sprint Tracking

Previous versions:

• 1.4 https://wiki.mozilla.org/FirefoxOS/Comms/1.4

2.0 Sprint 1 - May 9

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 406 [1] => Not Acceptable ) ) 1

2.0 Sprint 2 - May 23

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 406 [1] => Not Acceptable ) ) 1

2.0 Sprint 3 - June 6

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 406 [1] => Not Acceptable ) ) 1

2.0 Sprint 4 - June 20

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 406 [1] => Not Acceptable ) ) 1

2.0 Sprint 5 - July 4

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 406 [1] => Not Acceptable ) ) 1

Top 25 list for Comms

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 406 [1] => Not Acceptable ) ) 1