Firefox OS/Comms/Dialer/Sprint/v2.2-S10

Bugs

Status

• <POINTS>,0,0,0,0,0,0,0,0,0

Bugs Taken in Planning

Full Query

ID	Assigned to	Summary	Blocking b2g	Feature-b2g	Whiteboard	Status	Resolution
1060293		Remove dialer's buttons.css once gaia-button lands	---	No cf_feature-b2g	[planned-sprint c=6]	RESOLVED	WONTFIX
1100995	Gabriele Svelto [:gsvelto]	Tapping the # key causes l10n errors to be printed in the log	---	No cf_feature-b2g	[planned-sprint c=1]	RESOLVED	FIXED
1107781	Gabriele Svelto [:gsvelto]	Remove the call log db upgrade code	---	No cf_feature-b2g	[planned-sprint c=3]	RESOLVED	FIXED
1150910	Tamara Hills [:thills]	Opening call info view produces 'L10nError: "#type_l10n_id#" not found in en-US in app://communications.gaiamobile.org/dialer/index.html#keyboard-view'	---	No cf_feature-b2g	[planned-sprint c=3]	RESOLVED	WONTFIX
1151770	Tamara Hills [:thills]	[RTL][Dialer]The ellipsis shown at wrong side of text when user cheks info of a call log.	---	No cf_feature-b2g	[planned-sprint c=1][2.2-nexus-5-l]	RESOLVED	WORKSFORME

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

• Does not include Bugs Taken but not Completed.

Bugs Taken but not Completed

No results.

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

Bugs Taken During Sprint

Full Query

ID	Assigned to	Summary	Blocking b2g	Feature-b2g	Whiteboard	Status	Resolution
1150953	Doug Sherk (:drs) (inactive)	[RTL] Callscreen contact phone number "+" symbol is on the wrong side	2.2+	No cf_feature-b2g		VERIFIED	FIXED

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

All Issues for this Sprint

Full Query

ID	Assigned to	Summary	Blocking b2g	Feature b2g	Whiteboard	Status	Resolution
1060293		Remove dialer's buttons.css once gaia-button lands	---	---	[planned-sprint c=6]	RESOLVED	WONTFIX
1100995	Gabriele Svelto [:gsvelto]	Tapping the # key causes l10n errors to be printed in the log	---	---	[planned-sprint c=1]	RESOLVED	FIXED
1107781	Gabriele Svelto [:gsvelto]	Remove the call log db upgrade code	---	---	[planned-sprint c=3]	RESOLVED	FIXED
1150910	Tamara Hills [:thills]	Opening call info view produces 'L10nError: "#type_l10n_id#" not found in en-US in app://communications.gaiamobile.org/dialer/index.html#keyboard-view'	---	---	[planned-sprint c=3]	RESOLVED	WONTFIX
1150953	Doug Sherk (:drs) (inactive)	[RTL] Callscreen contact phone number "+" symbol is on the wrong side	2.2+	---		VERIFIED	FIXED
1151770	Tamara Hills [:thills]	[RTL][Dialer]The ellipsis shown at wrong side of text when user cheks info of a call log.	---	---	[planned-sprint c=1][2.2-nexus-5-l]	RESOLVED	WORKSFORME

6 Total; 0 Open (0%); 5 Resolved (83.33%); 1 Verified (16.67%);

• Does not include Bugs Taken but not Completed.

Bugs Redirected

Full Query

ID	Assigned to	Summary	Blocking b2g	Feature b2g	Whiteboard	Status	Resolution
1060293		Remove dialer's buttons.css once gaia-button lands	---	---	[planned-sprint c=6]	RESOLVED	WONTFIX
1100995	Gabriele Svelto [:gsvelto]	Tapping the # key causes l10n errors to be printed in the log	---	---	[planned-sprint c=1]	RESOLVED	FIXED
1107781	Gabriele Svelto [:gsvelto]	Remove the call log db upgrade code	---	---	[planned-sprint c=3]	RESOLVED	FIXED
1150910	Tamara Hills [:thills]	Opening call info view produces 'L10nError: "#type_l10n_id#" not found in en-US in app://communications.gaiamobile.org/dialer/index.html#keyboard-view'	---	---	[planned-sprint c=3]	RESOLVED	WONTFIX
1151770	Tamara Hills [:thills]	[RTL][Dialer]The ellipsis shown at wrong side of text when user cheks info of a call log.	---	---	[planned-sprint c=1][2.2-nexus-5-l]	RESOLVED	WORKSFORME

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

Daily Standup Meetings

• Current hosts: drs, gtorodelvalle, thills
• Hosts rotate every week.

1. If you're not available for a standup that you're scheduled to host, then ask for someone else to host instead for just that time.
2. Start by pinging everyone who should be participating.
3. List any administrative items you have, and then ask for more from other people (look at the Etherpad).
4. Look at the list of blockers and blocker nominations and see if there's anything new or that needs action. Mention these during this time.
5. Move to individual updates. Go alphabetically, in descending order.
6. If someone's update is taking longer than 3-4 minutes, you should generally cut them off and ask them to talk about it after the standup.
7. Copy the reports from the GDoc to the wiki page for that day. Use the Etherpad-to-Wiki converter to format it. You can just copy and paste the whole thing and the converter will do everything for you.
8. Ask the person who should be hosting the week after you if they'll be available. If not, move onto the next person.

Day 10:

FirefoxOS/Comms/Dialer/Sprint/v2.2-S10/2014mmdd-StandupNotes

Day 9:

drs

• Admin:
  • Focused on Lightsaber.
• Next steps:
  • Nothing new.
• Patches:
  • Nothing new.
• Reviews:
  • bug 1107781 - Remove the call log db upgrade code
    • r?
• Other:
  • Nothing new.

thills

• Admin -
  • focused on telemetry
• Bugs
  • bug 1151770 - put this for review.
• Uplifts:
• Reviews:
  • bug 1100995 - r+ Found a problem with this and sent ni back to gsvelto on this.
  • bug 1107781 - r+ Remove the call log db upgrade code

gsvelto

• Admin:
  • None
• Bugs:
  • bug 1060293 - Remove dialer's buttons.css once gaia-button lands
    • Started working on this
  • bug 1100995 - Tapping the # key causes l10n errors to be printed in the log
    • Landed
  • bug 1107781 - Remove the call log db upgrade code
    • Posted a new set of patches with properly upgraded reference workloads, waiting for review
  • bug 1124992 - [Dialer] not need to listen to telephonyCallGroup.onerror but handle promise
    • I’ve taken this bug at the request of the RIL team, it’s a minor API cleanup (still haven’t had time to work on it)
• Reviews
  • none

jlorenzo

• Absent/no report

Day 8:

drs

• Admin:
  • Focused on Lightsaber.
• Next steps:
  • Nothing new.
• Patches:
  • Nothing new.
• Reviews:
  • bug 1107781 - Remove the call log db upgrade code
    • r?
• Other:
  • Nothing new.

thills

• Admin -
  • focused on telemetry
• Bugs
  • bug 1151770 - put this for review.
  • bug 1154634 - we have a nom for this. I was ni and will try and bisect this today.
• Uplifts:
• Reviews:
  • bug 1100995 - r? Found a problem with this and sent ni back to gsvelto on this.
  • bug 1107781 - r? Remove the call log db upgrade code

gsvelto

• Admin:
  • None
• Bugs:
  • bug 1124992 - [Dialer] not need to listen to telephonyCallGroup.onerror but handle promise
    • I’ve taken this bug at the request of the RIL team, it’s a minor API cleanup (still haven’t had time to work on it)
  • bug 1100995 - Tapping the # key causes l10n errors to be printed in the log
    • Posted yet another patch to address the issue caused by the phone types whitelist
  • bug 1107781 - Remove the call log db upgrade code
    • Posted a new set of patches with properly upgraded reference workloads, waiting for review
• Reviews
  • none

jlorenzo

• Absent/no report

Day 7:

thills

• Admin -
  • focused on telemetry
• Bugs
  • bug 1151770 - put this for review.
• Uplifts:
• Reviews:
  • bug 1100995 - r? Found a problem with this and sent ni back to gsvelto on this.

jlorenzo

• Absent/no report

gsvelto

• Absent/no report

Day 6:

drs

• Admin:
  • Focused on Lightsaber.
• Next steps:
  • Nothing new.
• Patches:
  • Nothing new.
• Reviews:
  • bug 1107781 - Remove the call log db upgrade code
    • r?
• Other:
  • Nothing new.

thills

• Admin -
  • I wound up taking a half day of PTO yesterday as I’m sick.
  • focused on telemetry
• Bugs
  • bug 1151770 - I have prepared a patch and finishing up on tests right now.
• Uplifts:
• Reviews:
  • bug 1100995 - r?

jlorenzo

• Absent/no report

gsvelto

• Absent/no report

Day 5:

drs

• Admin:
  • Focused on Lightsaber.
• Next steps:
  • Nothing new.
• Patches:
  • Nothing new.
• Reviews:
  • Nothing new.
• Other:
  • Nothing new.

thills

• Admin -
  • focused on telemetry
• Bugs
  • bug 1151770 - Need to re-work this as the change broke some of the things in contacts. Working on this now.
• Uplifts:
• Reviews:
  • bug 1100995 - r?

gsvelto

• Admin:
  • None
• Bugs:
  • bug 1124992 - [Dialer] not need to listen to telephonyCallGroup.onerror but handle promise
    • I’ve taken this bug at the request of the RIL team, it’s a minor API cleanup
  • bug 1100995 - Tapping the # key causes l10n errors to be printed in the log
    • Posted a new patch which fixes the problem and also other underlying l10n issues
  • bug 1107781 - Remove the call log db upgrade code
    • Working hard on this one, I had to un-bitrot the patches but I’m still running into issues with the reference workloads so it might take longer than anticipated
• Reviews
  • none

jlorenzo

• Absent/no report

Day 4:

FirefoxOS/Comms/Dialer/Sprint/v2.2-S10/2014mmdd-StandupNotes

Day 3:

FirefoxOS/Comms/Dialer/Sprint/v2.2-S10/2014mmdd-StandupNotes

Day 2:

FirefoxOS/Comms/Dialer/Sprint/v2.2-S10/2014mmdd-StandupNotes

Day 1:

FirefoxOS/Comms/Dialer/Sprint/v2.2-S10/2014mmdd-StandupNotes

PTO

• drs: None, but focused on Lightsaber
• gsvelto: Thursday 9 and Friday 10
• jlorenzo: ?
• thills: None, but focused on Telemetry. Will probably be < 50% since Telemetry proj is kicking off

Retrospective

Retrospective Etherpad

Things we did well

• <drs> We technically got all of our 2.2 blockers done on time, though there may be more to come.
• <gsvelto> In spite of landing plenty of changes we didn't seem to have introduced any regressions (yet), test coverage is probably improving

Things we could do better

• <jlorenzo> Get the regression window more quickly, especially a couple of days before the deadline. I delegated to the contactors in Seattle. I could do it while you guys were still asleep. I'll remember that for the next FC milestone
  • <drs> It's sometimes actually faster for us to get it ourselves. This is a sign that this process could be a lot better.
  • <thills> maybe a higher level thing, but we should have a cutoff point where we don't allow adhoc testing after a certain point. When it gets really close to a release, we should just test to the plan. Maybe front load our schedule with ad-hoc testing. It becomes hard to predict a release date with no blockers when there is ad-hoc testing at the end.