Gaia/SMS/Scrum/FxOS-S7: Difference between revisions

/* Retrospective
(/* Remaining points and burndown chart)
(/* Retrospective)
 
(8 intermediate revisions by 2 users not shown)
Line 12: Line 12:


==== Remaining points and burndown chart ====
==== Remaining points and burndown chart ====
[http://chart.apis.google.com/chart?chs=600x250&cht=lxy&chtt=Burndown%20for%20sprint%20FxOS-S7&chxt=x,y&chxl=days&chdl=Estimated|Actual&chco=FF0000,00FF00&chd=t:-1|8,0|-1|8,8,7,7,7,7,_,_,_,_,_&chxr=0,1,11,1|1,0,8,1&chds=0,8&chm=s,0000ff,1,-1,5 google chart api url for Sprint FxOS-S7]
[http://chart.apis.google.com/chart?chs=600x250&cht=lxy&chtt=Burndown%20for%20sprint%20FxOS-S7&chxt=x,y&chxl=days&chdl=Estimated|Actual&chco=FF0000,00FF00&chd=t:-1|8,0|-1|8,8,7,7,7,7,7,7,7,7,_&chxr=0,1,11,1|1,0,8,1&chds=0,8&chm=s,0000ff,1,-1,5 google chart api url for Sprint FxOS-S7]
[[File:Sms-sprint-FxOS-S7-burndown-chart.png|thumb|600px|left|Burndown chart]]
[[File:Sms-sprint-FxOS-S7-burndown-chart.png|thumb|600px|left|Burndown chart]]
{| class="wikitable"
{| class="wikitable"
Line 38: Line 38:
|-
|-
! Day 7
! Day 7
|
| 7
|-
|-
! Day 8
! Day 8
|
| 7
|-
|-
! Day 9
! Day 9
|
| 7
|-
|-
! Day 10
! Day 10
|
| 7
|-
|-
! End
! End
Line 278: Line 278:


=== Day 7: 16th September ===
=== Day 7: 16th September ===
====Julien====
Again a slow day, I got busy with external things...
* clarified the possible solutions in {{Bug|1190613}} (for System FE team)
* looked at the code for the mozContacts API for {{Bug|1114525}}, to have an idea of the needed work
* started some background work to avoid updating the thread node for draft changes.
* started reviewing Oleg's patch in {{Bug|1176976}} again
Today:
I want to:
* handle review/feedback/NI queue
* start work on the low storage condition
If all this moves forward well, I could:
* continue the prototype caching the thread list to a single db (including contacts/drafts/etc).
====Steve====
PTO
====Oleg====
PTO
=== Day 8: 17th September ===
=== Day 8: 17th September ===
====Steve====
* {{Bug|1179628}} - [Messages][NG] Lay out Settings service structure
** Start to plan the possible layout of the general settings service
* {{Bug|1201016}} -  [Messages][NG] Migrate the current Message manager event handling to NGA.
** Implemented message event handling in inbox. Since it'll need bridge lib and related scripts in cold launch patch, I'm using raptor to measure how much penalty it may bring.
* Leave some question about the conversation service/service initializer
Today:
* Address the feedback in message event handling patch and fix the duplicate event issue.
* Layout for settings service
====Julien====
Again a slow day, I got a lot busy with external things :/
* spent a lot of time on Oleg's patch in {{Bug|1176976}} but got interrupted a lot, so it's still not finished. I'll resume today for sure.
:(Oleg) Sorry for the huge patch :/
Today:
I want to:
* handle review/feedback/NI queue
* start work on the low storage condition
If all this moves forward well, I could:
* continue the prototype caching the thread list to a single db (including contacts/drafts/etc).
====Oleg====
* {{Bug|1176976}} - [Messages][Drafts] Remove the draft saving/replacing action menu
** Got some feedback from Julien, will read and reply if needed (in review).
* {{Bug|1198266}} -  [Messages] Use ConversationService in the application
** Took a closer look to the performance with the WIP, we're regressing ~200ms in visuallyLoaded, I think we can shave a bit here, but don't think too much because of all this bridge machinery involved, and obviously regress on fullLoaded, but I'm not too worried about the latter. The latter mostly regressed due to slow initialization of alwaysLowered window - started to profile on the dedicated test-case app - at least to involve relevant people and move the solution for this problem forward.
**: (Julien) we don't really need the alwaysLowered window now that we don't to split views anymore; I mean, for activities it's still nice to have, but not as much needed.
**: (Oleg) mmm, my main point is that we can't start use any services on startup that depends on mozShims inside iframe - it's just too slow. So we'll likely put them to window context. Yeah, we either can leave them there or upgrade later to alwaysLowered - but agree now it's not a priority :( The main (only?) benefit of this window is to save some time when we navigate between views in "split" mode, that's not going to happen for v2.5.
Today:
* Handle bug mail;
* Will handle review/feedback/need-info requests;
* Will work on review comments and assigned bugs. Will work mostly on this today as I have some feedback already :)
=== Day 9: 18th September ===
=== Day 9: 18th September ===
====Steve====
* {{Bug|1179628}} - [Messages][NG] Lay out Settings service structure
** Left some thought on bugzilla, will give a WIP for early feedback.
* {{Bug|1201016}} -  [Messages][NG] Migrate the current Message manager event handling to NGA.
** Seems some regression for cold launch and memory is hard to avoid, not sure we should take this for inbox in 2.5.
**: (Julien) I think we need to move forward; again, worst case is we take the services in the same window, but best case is Gecko engineers can decrease the memory usage of workers (if that's the only memory issue of course).
Today:
* Read the replay about the conversation service.
* WIP for settings client layout
* Review rishav's patch
====Julien====
* still spent some time on Oleg's patch in {{Bug|1176976}} but still not finished
* answered rishav's requests in {{Bug|1183074}} (explaining current state for group MMS) and {{Bug|1180470}} (describing how the "send read report" toggle could work)
* replied to Steve's idea about the Settings shim too.
Today:
I want to:
* handle review/feedback/NI queue
* start work on the low storage condition
If all this moves forward well, I could:
* continue the prototype caching the thread list to a single db (including contacts/drafts/etc).
====Oleg====
* {{Bug|1176976}} - [Messages][Drafts] Remove the draft saving/replacing action menu
** Fixed ongoing review comments and affected unit , waiting for the rest before pushing updates (in review).
* {{Bug|1198266}} -  [Messages] Use ConversationService in the application
** Replied to the questions at GitHub and tried to explain the idea in general (in progress, awaiting feedback).
Other:
* Handled bugmail/other ;
Today:
* Will handle review/feedback/need-info requests;
* Will work on review comments and assigned bugs.
=== Day 10: 21st September ===
=== Day 10: 21st September ===
====Steve====
* {{Bug|1179628}} - [Messages][NG] Lay out Settings service structure
** Create a WIP for that implement settings client mmsSize & maxConcat methods and use it for compose init. Will replace the mmsSize in activity handler.
* {{Bug|1201016}} -  [Messages][NG] Migrate the current Message manager event handling to NGA.
** Gave some more testing about the new message event handling and will work on the unit test.
* Clean up the ni and review.
Today:
* Read the replay about the conversation service.
* Complete the prototype of settings client layout.
====Julien====
Slow day because I spent a lot of time working on a slidedeck for last week-end's event.
Note: tomorrow afternoon I'll be in the train and finish early, wednesday I'm in PTO.
* still spent some time on Oleg's patch in {{Bug|1176976}} but still not finished; finished the code part, will work on the testing part today.
* did some bug triaging for new bugs
Today:
I want to:
* continue handling review/feedback/NI queue
* start work on the low storage condition
If all this moves forward well, I could:
* continue the prototype caching the thread list to a single db (including contacts/drafts/etc).
====Oleg====
Will take PTO for the second half of the day tomorrow.
* {{Bug|1176976}} - [Messages][Drafts] Remove the draft saving/replacing action menu
** Replied to new review comments, started to fix what is needed (in review).
* {{Bug|1198266}} -  [Messages] Use ConversationService in the application
** No progress (awaiting feedback).
Other:
* Investigated "{{Bug|1205988}} - [Messages]Enter Messaging  Settings view, then device receives a MMS, but it can't back to Messages  view when user taps the notification";
* Investigated "{{Bug|1203886}} - The back button in sms conversation view does not always work"
Today:
* Will handle review/feedback/need-info requests;
* Will work on review comments and assigned bugs.
== Demos ==
== Demos ==
== Retrospective ==
== Retrospective ==
No demo this time
===Previous sprints' actions===
From 2.1S3:
* Look into VM with gaia dev environment
*: Nothing more done in this sprint
From 2.1S5:
*  in planning for sprint N, we pick some items we want to do in sprint  N+1 to ask early questions to UX and Designers (esp refresh bugs, but  also bugs with UX changes)
*  we'll add screenshots of panels in Wiki, with the various cases for  these panels, to help analyzing change impacts and not forgetting things
*: Oleg started this: https://wiki.mozilla.org/Gaia/SMS/Current_App_State
From 2.2S4:
* undercommit in the sprints.
* use bugs and github's PR for spec definition and changes
From 2.2S14:
* move more discussions to #gaia
* figure out 2.5 features for SMS
From FxOS-S3:
* split patches as much as we can when we develop it, and split bugs as much as we can when planning them.
From FxOS-S7:
* stand-up at 11:30am CET / 5:30pm Taipei
===What was good in the last sprint===
* I could review Oleg's patch about draft handling ;) This is good because I really want this in the next version, and I feel the next round of review will be easier :p
* We have new contributor(?)
** yeah, Stéphane :) he's actually having interviews to enter our team these days \0/ He is a positive guy, I'm happy with this decision :)
** Wow, good news :)
** on the same note, we have 2 good candidates now; we have another one to start soon. (Note: I'll remove this from the etherpad before putting on wiki :p)
* I was finally able to wrap up something with new services and window context that can potentially be landed in master some day :)
* Rishav is back.
===What was bad in the last sprint===
* it feels like we did the smallest amount of work ever :/
** same feeling; but when I looked at last planning, I can see a lot of points were for investigation, so I think it was as expected ?
** Right + PTOs, so yeah, just expressed my feeling :)
* I don't really like how we planned low storage
** You mean we had to allocate points for it during last planning?
** No, by "we" I mean "the managing team that decided to do it"; the spec and discussions lasted so much time... you don't see everything ;)
** Ah, good to know :)
===Any questions===
* So it's the last NGA-only sprint, right? October is for blockers? (just confirming that nothing has changed)
** Actually in this sprint we'll need to focus on low storage first.
** Yep, got it.
** Then about blockers, we have a lot, so maybe it could be good to take one or 2 (political reasons :p).
** Should we also consider blocker outside message?
** not yet, I think. Only when our blockers are at 0. But if you have time I'm sure the dialer/contacts team would be glad ;)
===Actions for next sprint===
* the time for the stand-up does not work very well for me after all; I'd like to try later in  the day (like 1:45pm CET, don't know if this works for Steve)
** I usually in Gym between 12 - 13.30 +- 20 min (Monday, Wednesday, Friday).
** 2pm then ? I'd like to try coming to the office earlier, and the standup at 9 is preventing me from preparing usually :)
** 2pm is ok for me, when do you usually come to the office? :)
** I see it's really late for Taipei. Maybe 11:30am ? or earlier ? I usually arrive around 11 but I'd like to arrive earlier :)
** anything before 12 is good for me :)
** 11:30 works for me, so start from tomorrow?
** tomorrow I'm not here :p but otherwise yep
** When Julien is not there, I'm fine with any time works best for you, Steve :)
Confirmed users
820

edits