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

Gaia/SMS/Scrum/FxOS-S7 (view source)

Revision as of 07:38, 17 September 2015

2,667 bytes added , 17 September 2015

m

→‎Day 8: 17th September

Azasypkin

Confirmed users

383

edits

@@ Line 298: / Line 298: @@
 === 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 10: 21st September ===
 == Demos ==
 == Retrospective ==