Confirmed users
3,816
edits
EngineeringProductivity/Meetings/2011-09-26: Difference between revisions
Jump to navigation
Jump to search
EngineeringProductivity/Meetings/2011-09-26 (view source)
Revision as of 16:50, 26 September 2011
, 26 September 2011→RoundTable
| Line 1: | Line 1: | ||
= RoundTable = | = RoundTable = | ||
* Discussion on projects, priority and polish | |||
** Two phase solution - development & release | |||
** Having well-defined priorities | |||
** Having well-defined end goals for each phase of a project | |||
** Handling bumping projects and shifting priorities | |||
* '''Outcome:''' What can we do (as a team) to help us with this? | |||
* '''Outcome:''' What can Clint do (as team lead) to help with this? | |||
'''Goals:''' | |||
* mobile automation | |||
** get from 25% failure rate to <5% rate (desktop parity that is) | |||
** make it easier for developers to run and debug tests with tools and hardware | |||
*** Make targets for all tests | |||
*** better documentation for all tests and tools | |||
* performance | |||
** aid in future xperf and pageloader modifications | |||
** keep talos and AMO perf up to date with firefox changes (i.e. missing application.ini, etc..) | |||
** resolve and triage perf bugs | |||
* specialpowers | |||
** finish the mochitest harness | |||
** ensure existing work done on tests lands (i.e. content patches from :jdm) | |||
** make a specialpowers-core for quit, prefs and logging. Good for talos, etc... | |||
** NOTE: this will make us 100% harness and about 75% test complete. | |||
* mozbase | |||
** have working prototype with releng for talos, mochitest, reftest, xpcshell | |||
** resolve location and process for mozprocess, mozprofile, etc... | |||
** land any prerequisite patches and toolchains | |||
** NOTE: I suspect we won't get mozbase landed 100%, but we should be getting close | |||
** get virtualenv on m-c | |||
** coordiante with Release Engineering on mobase/mozharness efforts | |||
** get talos on mozbase packages | |||
** get automation.py on mozbase packages | |||
** update documentation | |||
** communicate about this! | |||
** continue to added needed features to mozbase packages | |||
** bugs are at https://bugzilla.mozilla.org/buglist.cgi?resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=mozbase&list_id=1352142 | |||
** [MAYBE] split up the mozmill repo | |||
* manifests | |||
** mochitest-plain manifests | |||
* MozMill: | |||
** get 2.0 out the door for real and support it | |||
** possibly help refactor mozmill-automation if desired | |||
** Make Mozmill e10s ready (probably working with :ahal) | |||
* W3C browser testing work | |||
** TBD | |||
* B2G | |||
** Get phase 1 of platform level test framework created | |||
** Aid with build system needs (joint with releng?) | |||
* SpeedTests | |||
** Expanding to new browsers | |||
** Expanding tests | |||
** Maintenance | |||
* Eideticker | |||
** Complete test framework side | |||
** Investigate using another card? | |||
* WOO | |||
** Shepherd through secreview | |||
* Templeton | |||
** Find/fix | |||
* bughunter | |||
** Greater integration with soccoro? | |||
* User Responsiveness Regression Test | |||
** Complete harness for this | |||
** Shepherd through buildbot and/or mozharness integration | |||
* Better community outreach | |||
** Have volunteers involved in community stewards effort | |||
** Have a blogging goal for the team? | |||
* Better process/priority clarity for each project | |||
** TBD (see above) | |||
= Goals = | = Goals = | ||