|
|
| Line 67: |
Line 67: |
| == Retrospective == | | == Retrospective == |
| === Actions taken from last sprint === | | === Actions taken from last sprint === |
| *As Raptor is not useful right now for integrating with Marionette [https://bugzilla.mozilla.org/show_bug.cgi?id=1169775 1169775] we need to:
| |
| **AP1:Raise this issue in the NGA Program Management meeting and ask for deadline. '''Done''': Borja talked to Eli and he said that this bug will be prioritized in his team (although in bugzilla there has not been any priority change). Besides Raptor team offered his help to prioritize the problems that we could face when measuring Contacts performance.
| |
| **AP2:In the meantime, we can try to add measures and print them with marionette. '''Done''': Alberto has already worked on it, we need to test it.
| |
| *Development Synchronization is necessary: weekly meetings, or weekly mails so everybody is aware of the changes and progress in the NGA libraries.
| |
| **AP3:Raise this issue in the NGA Program Management meeting. '''Done''' In Whistler it will be agreed the best way to do it with development team in charge of the NGA migration but for the time being, Vivien sent a complete update via dev-gaia list last 19th June.
| |
| ***We should open a follow-up task in next sprint to confirm that it happens after Whistler
| |
| *When landing the new code, we are not involving QA team or doing any type of regression tests, besides we should not forget the FTU part that also involves Contacts functionality (Importing, Merging)
| |
| **AP4:We need to plan with QA team how to plan and handle all this work.
| |
| *AP5:Include a Contacts demo in the Agenda for Demo Sync Up meeting in Whistler (Details in https://etherpad.mozilla.org/nga) '''Done'''
| |
|
| |
|
| === Things that went well === | | === Things that went well === |
| === Things that went not that well === | | === Things that went not that well === |
| === Actions for this sprint === | | === Actions for this sprint === |