666
edits
FxOS Portfolio Management: Difference between revisions
2.6
(delete plan project) |
(2.6) |
||
| Line 72: | Line 72: | ||
| On Hold | | On Hold | ||
| The project or deliverable has been placed on hold. | | The project or deliverable has been placed on hold. | ||
|} | |||
==Current 2.6 Release== | |||
{| class="wikitable" style="width: 85%; margin: auto;" | |||
| Action/Agenda Item | |||
| Assignee(s) | |||
| Status | |||
| Notes | |||
|- | |||
| Continuous Integration Program | |||
| Julie McCracken | |||
! style="color:#00EC00;" | On Target | |||
| This week: | |||
''Testing Improvements'' | |||
'''Test Matrix''' | |||
* The test matrix meeting held at Mozlando wasn’t well attended because of a 2.6 scope meeting scheduled at the same time, but progress was still made on the matrix. Team members developed rules for when certain testing frameworks should be used for each type of test. A little more work will be done to complete it, and then it will undergo review for feedback. | |||
'''GIP to GIJ Conversions''' | |||
* 26 conversions to go, down from 37 two weeks ago. 17 are unassigned. Module owners will be getting weekly notifications to remind them of the integration tests that remain to be converted. | |||
* GIP to GIJ Test Conversion Bug List | |||
* Question came up regarding the writing of additional python tests within the QA team. Maintainability of python tests is the issue. Shouldn’t write new ones in Python. If there are shortcomings in MJS that doesn’t permit the testing, bugs should be filed. | |||
'''Intermittents''' | |||
* 8 intermittents still need to be fixed but only 2 of them remain unassigned. Module owners to be alerted when identified. | |||
* [https://bugzilla.mozilla.org/buglist.cgi?bug_id=1221876%2C1163853%2C1222355%2C1216273%2C1223321%2C1192249%2C1220487%2C1191036&list_id=12691492 Intermittent Failures Bugs] | |||
'''Tests that work on mulet but fail on device.''' | |||
* About 10 bugs have been opened for these tests and none have been assigned. Module owners to be alerted. | |||
* [https://bugzilla.mozilla.org/buglist.cgi?bug_id=1223840%2C1223905%2C1223899%2C1223888%2C1223850%2C1223848%2C1223851%2C1223868%2C1223871%2C1223908&list_id=12691475 Test Works on Mulet; Fails on Device Bug List] | |||
'''Marionette Improvements''' | |||
* Team members met at Mozlando and worked together on removal of python from the Marionette harness, which is expected to be completed in Q4. Effort to remove python from Marionette harness has been started. | |||
* Two sessions were held to provide training and assistance with Marionette testing, a Marionette 101 session, and a follow-on session for Q&A and “office hours” support. Both sessions were well attended. | |||
* Next steps: planning for bitbar automation work! Bitbar contract renewal in the works. | |||
'''Emulator Improvements''' | |||
* Hacking session at Mozlando was successful. Assistance was provided by build and release team and automation team members. 2 bugs were closed out. | |||
* Module owners need to be aware that ICS is going away and that they should move their tests to KK. | |||
* Discussed porting of emulator to either L or M, and many pros and cons were brought up. Lack of resources was also noted. Decision made to continue working on KK issues for the time being. | |||
|- | |||
| Train Model Implementation/Rel Eng work | |||
| Mahe | |||
| New | |||
| OTA Branch | |||
* OTA branch is set up. | |||
* We still need to decide who will do the uplifts . That is still tbd. | |||
|- | |||
| Foxfooding Program | |||
| Jean/Mahe | |||
| New | |||
| This week: | |||
* Discussion on foxfooding held at Mozlando with Ari re. focusing more heavily in foxfooding program. There were some strategic next steps proposed. These are tbd but will be shared once we lock these down | |||
* Ari agreed that foxfooding is critical in the new connected devices realm where we still need a development reference device (that may or may not be a phone). | |||
* Most foxfooding bugs are prioritize, still some remaining.. Will publish [https://docs.google.com/spreadsheets/d/1KnWw888bX6SnsMvBZye-rqpytL44CwHGcE7MfHfO_bQ/edit#gid=0 2.6 Non blocking Bugs] to wiki by end of week.. | |||
* Avoid Feature Work from foxfooding feedback | |||
* Need Tamara/Russ’s support for building foxfooding app to report UUID | |||
* need to come up with communication to foxfooders about next steps, value-add, how we plan to move forward. (Jean/Faramarz) | |||
|- | |||
| Architecture Change | |||
| Maria | |||
| New | |||
| This week: | |||
* FE/BE and views split: | |||
** A meeting will be scheduled with Ari and David Bryant to prioritise and see what it makes sense to focus on after last week’s announcement. (Jan) | |||
** During this week the FE/BE and views split will be on standby although we will finish the move of Contacts app in NGA branch to dev-apps and the isolation of Contacts from Communications app | |||
* Question around settings/system app changes for architecture? | |||
** Francisco to experiment on settings app himself and help test/validate for a decision | |||
** Maybe folks working on sms can refocus on settings | |||
** Media apps are being followed up with Joe | |||
*** Need to understand value for timeline | |||
* Web Components: We have decided not to implement any changes in Gaia regarding web components but just focusing on the fxos-components organisation ([https://bugzilla.mozilla.org/show_bug.cgi?id=1230494 Bug 1230494]). What we have done so far is: | |||
** Moved to a new organisation: fxos-components | |||
** Migrated some components from gaia-* to fxos-*: When doing so, we don’t only change the name but also: | |||
*** Improve documentation, examples, etc… | |||
*** Publish the components in NPM3 | |||
*** There are still some pending components… the next step is completing the migration | |||
*** After completing the migration, we will test the end-to-end flow of using npm3 for expressing application dependencies in one app (music or camera). | |||
*** Based on that, we will decide if it’s worth it to apply to all the gaia apps, prioritise, etc… | |||
** UX support: In Orlando meeting, UX want to put minimal efforts on spec until there is more clear info about target devices. | |||
* Data Sync | |||
** Stage 2: "Read-only history sync on the phone” (as part of Firefox Sync) is almost completed, just pending some bugs (specially [https://bugzilla.mozilla.org/show_bug.cgi?id=1232276 1232276] that it’s a priority for 2.5 Smart TV) and get the feature available to foxfooders | |||
** Planned 2.6 scope needs to be reconsidered. | |||
*** Stage 3: "Read-write history sync and passwords sync on the phone" | |||
*** Media files synchronization looks still important for connected devices but the approach that we were taking (via FileSystemProvider API) might not be valid anymore, it really depends on the product, architecture and platform choice (on hold) | |||
*** Local and remote Backup/Restore: although it does not seem a priority, it’s on hold until there is clarity on our strategy around smartphones | |||
*** Contacts Sync. | |||
* Telemetry: | |||
** We continue working on it but no Product Manager, last Roadmap for 2.6 [https://wiki.mozilla.org/Firefox_OS/Metrics#Roadmap] | |||
** There is still a lot work to do, but some features should be reconsidered like A/B testing | |||
** We need prioritization of the features, too many features and there are dependencies with platform (just confirmed with Tamara that there is only one dependency and it seems not difficult to implement, [https://bugzilla.mozilla.org/show_bug.cgi?id=1232453 1232453]) | |||
|} | |} | ||