Firefox OS/Comms: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(2 intermediate revisions by 2 users not shown)
Line 182: Line 182:
</bugzilla>
</bugzilla>


=Top 25 list for Comms=
=Team Backlog=
*Tracking-b2g:+  (http://goo.gl/3RzYRR)
 
<bugzilla>
<bugzilla>
     {
     {
         "whiteboard":"[priority]",
         "cf_tracking_b2g":"+",
         "status":["NEW","REOPENED","UNCONFIRMED","ASSIGNED"],
         "status":["NEW","REOPENED","UNCONFIRMED","ASSIGNED"],
         "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", " Gaia::Network Alerts"],
        "include_fields": "id, summary, component, status, resolution, assigned_to, whiteboard, cf_blocking_b2g, cf_feature_b2g"
    }
</bugzilla>
*Tracking-b2g:backlog  (http://goo.gl/TdRcK8)
<bugzilla>
    {
        "cf_tracking_b2g":"backlog",
        "status":["NEW","REOPENED","UNCONFIRMED","ASSIGNED"],
        "component":["Gaia::Contacts","Gaia::SMS","Gaia::Dialer","Gaia::Wappush","DOM:_Contacts","Gaia::Cost_Control", " Gaia::Network Alerts"],
         "include_fields": "id, summary, component, status, resolution, assigned_to, whiteboard, cf_blocking_b2g, cf_feature_b2g"
         "include_fields": "id, summary, component, status, resolution, assigned_to, whiteboard, cf_blocking_b2g, cf_feature_b2g"
     }
     }
</bugzilla>
</bugzilla>

Latest revision as of 06:26, 10 April 2015

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]. Will migrate these to flag tracking-b2g soon.
    • blocking-b2g == backlog (http://goo.gl/wxW7fJ)


To be triaged

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

Past Releases

2.0 Velocity Chart

Sprint backlog

2.2 S1 (~12/05)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.2 S2 (~12/19)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


2.2 S3 (~1/9)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.2 S4 (~1/23)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.2 S5 (~02/06)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.2 S6 (~2/20)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.2 S7 (~3/06)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.2 S8 (~3/20)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.2 S9 (~4/03)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.2 S10 (~4/17)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.2 S11 (~5/01)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.2 S12 (~5/15)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Team Backlog

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);