Confirmed users
820
edits
Gaia/SMS/Scrum/2.2S13: Difference between revisions
Jump to navigation
Jump to search
Day 11: 19th May
Steveck324 (talk | contribs) |
(Day 11: 19th May) |
||
| Line 446: | Line 446: | ||
=== Day 11: 19th May === | === Day 11: 19th May === | ||
====Steve==== | |||
* {{Bug|1162031}} - [Messages][New Gaia Architecture] use the bridge with a shared worker | |||
** Await for Wilson's update about the busy service issue and asking feedback in {{Bug|1163955}} | |||
* {{Bug|1163955}} for this async promise base Drafts | |||
** Asking for the early feedback about the drafts implementation in inbox view. I listed 2 approaches about always access drafts by bridge and create a cache for drafts. | |||
**: (Julien) I have several thoughts already but I'll add them soon on the bug; but mostly I don't think we need to workaround performance issues yet -- mostly report them. For example Francisco told me that the _first_ postMessage with a worker is very long, but that this should/will be fixed. | |||
**: (Oleg) Then we should probably notify master dogfooders if any that performance is going down :) Oh I also see new raptor tests on Treeherder - won't it block us from landing (though we can probably do it manually without autolander)? | |||
* Creating another meta bug for moving Threads into service and follow bug for implantation details | |||
**: (Julien) I only wonder if we should not wait for having the DB ? Or do you think this is needed to have the service (even without DB) before moving forward? | |||
**: (Oleg) I'd say we need service with API that will be the same when we have DB (ideally :)), but probably need your update about local DB to better understand how it will work and what data it will contain. | |||
**: (Julien) I think we need to create the API just like we would do for a server API; so maybe starting with an etherpad to decide how the API should look like ? | |||
**: (Steve) I have the same thought like Oleg said that it might be the same when we have DB, but maybe you have another thought about the DB implementation | |||
**: (Julien) Oleg says: we need to have the same API than when we'll have the DB; you say: we'll have the same API than we have now when we'll have the DB. Not the same ;) | |||
**: (Oleg) We can discuss on etherpad to avoid confusion then. I mainly interested in what info about thread local DB will have | |||
**: (Steve) Ah , ok I misunderstood it :p | |||
**: (Julien) Steve, can you take the lead of starting the etherpad about this? | |||
**: (Steve) https://etherpad.mozilla.org/ng-message-threads-api | |||
* {{Bug|1161985}} - [Messages][NG] Split recipient and non-compose related styling from compose.css | |||
** R+ and landed on master. | |||
Today: | |||
* Create bugs for moving Threads/Drafts to server | |||
* Some tasks for background | |||
** Fix the attachment menu for closing the option menu manually | |||
** gaia-component stuff | |||
** file loading in Template.js | |||
====Julien==== | |||
I mostly read through my mail and bugmail. | |||
Today: | |||
I want to: | |||
* do reviews | |||
* start looking at little-browser | |||
If all this moves forward well, I could: | |||
* continue the prototype caching the thread list to a single db (including contacts/drafts/etc). | |||
* I'd like to work on the deduplication logic for network alerts, it seems important for users ({{Bug|1067938}}) | |||
====Oleg==== | |||
* {{Bug|1162027}} - [Messages][New Gaia Architecture] extract inbox/index.html | |||
** Prepared patch, asked for feedback (awaiting feedback/in progress). | |||
** Playing with composite startup.js, not sure if I can come up with something smart in this PR. | |||
* {{Bug|1127398}} - [Messages] Display existing thread when sending a message using phone-number-/email-link context menu | |||
** Rebased on the latest master, waiting for "{{Bug|1153885}} - [Messages] Remove Utils.getContactDisplayInfo". | |||
**: (Julien) maybe you can try to a little more actively help the contributor? Like asking on the bug how it goes, etc? (I can switch the mentoring to you :) ) | |||
**: (Oleg) Hah, I talked to him on GitHub mostly :) | |||
**: (Julien) if you're still in contact with him on github it's fine :) | |||
Other: | |||
* Reviewed "{{Bug|1161985}} - [Messages][NG] Split recipient and non-compose related styling from compose.css"; | |||
* More discussion on "new" integration test approach with Johan - getting closer; | |||
* Tried to run Simulator 3.0 in WebIDE with custom profile and provided contributor with the steps. | |||
* Noticed pretty sever graphic (probably) issue in sms - jumping and black squares when user navigates back from composer to inbox and save/discard draft dialog was displayed - will check again on the latest PVT and file a bug if it's still the case. | |||
**(Steve) Isn't it solved by backing out {{Bug|1162383}}(from the information in {{Bug|1164357}})? | |||
**(Oleg) I guess no, I've used the latest PVT build it should have contained that back out I think | |||
**(Steve) Hmm but I can't not reproduce it from PVT build in last Friday, anyway I think QA should verify this since it's marked as resolved | |||
**(Oleg) Honestly they look like different issues, but can't say for sure :) Will check again | |||
Today: | |||
* Will handle review/feedback/need-info requests; | |||
* Will work on review comments and assigned bugs. | |||
=== Day 12: 20th May === | === Day 12: 20th May === | ||
=== Day 13: 21st May === | === Day 13: 21st May === | ||