Firefox OS/Comms: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 107: Line 107:
         "target_milestone":"2.0 S5 (4july)",
         "target_milestone":"2.0 S5 (4july)",
         "component":["Gaia::Contacts","Gaia::SMS","Gaia::Dialer","Gaia::Wappush","DOM:_Contacts","Gaia::Cost_Control"],
         "component":["Gaia::Contacts","Gaia::SMS","Gaia::Dialer","Gaia::Wappush","DOM:_Contacts","Gaia::Cost_Control"],
         "include_fields": "id, summary, component, status, resolution, assigned_to, depends_on, blocks, whiteboard, cf_blocking_b2g, cf_feature_b2g, target_milestone"
         "include_fields": "id, summary, component, status, resolution, assigned_to, whiteboard, cf_blocking_b2g, cf_feature_b2g"
     }
     }
</bugzilla>
</bugzilla>

Revision as of 04:04, 4 July 2014

Team Backlog

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

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

  • 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]
  • 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

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

Message

Dialer

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)

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

Sprint Tracking

Previous versions:

2.0 Sprint 1 - May 9

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

2.0 Sprint 2 - May 23

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

2.0 Sprint 3 - June 6

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

2.0 Sprint 4 - June 20

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

2.0 Sprint 5 - July 4

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Top 25 list for Comms

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1