Confirmed users
1,225
edits
Gaia/New-Architecture-Program/Contacts/NGA SP3: Difference between revisions
Jump to navigation
Jump to search
Gaia/New-Architecture-Program/Contacts/NGA SP3 (view source)
Revision as of 10:22, 17 June 2015
, 17 June 2015→Actions taken from last sprint
| Line 50: | Line 50: | ||
**AP1:Raise this issue in the NGA Program Management meeting and ask for deadline | **AP1:Raise this issue in the NGA Program Management meeting and ask for deadline | ||
**AP2:In the meantime, we can try to add measures and print them with marionette. | **AP2:In the meantime, we can try to add measures and print them with marionette. | ||
*Development Synchronization is necessary: weekly meetings, or weekly mails so everybody is aware of the changes and progress in the NGA libraries. | *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 | **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 | ||
***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) | *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. | **AP4:We need to plan with QA team how to plan and handle all this work. | ||