MozillaWiki

Platform/2014-Q4-Goals-ByTheme: Difference between revisions

Page Discussion

Platform/2014-Q4-Goals-ByTheme (view source)

Revision as of 00:08, 14 October 2014

2,444 bytes removed ,  14 October 2014
→‎Platform
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Platform =
= Platform =
For Q4, the team decided to reformat the goals to demonstrate if they served a particular Product or more generally the Web Platform. We also wanted to call out high level themes around areas of focus. We developed similar theme buckets for the Engineering Operations goals.
== Gecko Engineering Goals ==
== Gecko Engineering Goals ==
For Q4, the team decided to reformat the goals to demonstrate if they served a particular Product or more generally the Web Platform. We also wanted to call out high level themes around areas of focus.


===Firefox Desktop===
===Firefox Desktop===
Line 118: Line 119:
* Web Engineering
* Web Engineering
**'''airmo'''
**'''airmo'''
*** {{ok|}} prototype self-service publishing
*** {{ok|}} prototype self-service publishing - e.g. getUserMedia-based new hire video recording, user uploads of pictures and videos
**** e.g. getUserMedia-based new hire video recording, user uploads of pictures and videos


* SUMO/Input
* SUMO/Input
** Implement v1.0 of BuddyUp, the live support app for FirefoxOS, and integrate it with existing SUMO web app.
** Implement v1.0 of BuddyUp, the live support app for FirefoxOS, and integrate it with existing SUMO web app.
** Update SUMO forums.
** Update SUMO forums.
* Release Engineering / Release Operations / Developer Services
** Support Windows 64 initiatives as needed.


====Theme: Tool Development and Automation====
====Theme: Tool Development and Automation====
Line 138: Line 141:
* Web Engineering
* Web Engineering
**'''crash-stats'''
**'''crash-stats'''
*** {{ok|}} begin migrating subsystems to AWS
*** {{ok|}} begin migrating subsystems to AWS - e.g. migrate hbase to S3, architect cloud infra, build production-quality AMIs
**** e.g. migrate hbase to S3, architect cloud infra, build production-quality AMIs
*** {{ok|}} enhance processor flexibility - e.g. deploy processor2015, enhance tooling for developing post-crash classifiers, prototype alternate processing pipelines
*** {{ok|}} enhance processor flexibility
*** {{ok|}} enhance search functionality - e.g. pull users from postgres search so we can shut it off, upgrade ES to 1.x, data dumps of search results
**** e.g. deploy processor2015, enhance tooling for developing post-crash classifiers, prototype alternate processing pipelines
*** {{ok|}} enhance search functionality
**** e.g. pull users from postgres search so we can shut it off, upgrade ES to 1.x, data dumps of search results
**'''elmo'''
**'''elmo'''
*** {{ok|}} continue progress towards buildbot retirement
*** {{ok|}} continue progress towards buildbot retirement - e.g. migrating diff/compare tools to a10n, migrate remaining buildbot steps to a10n
**** e.g. migrating diff/compare tools to a10n, migrate remaining buildbot steps to a10n
 
* DXR
** {{ok|}} Continue improving infrastructure.
*** For example: [https://bugzilla.mozilla.org/show_bug.cgi?id=1045183 move file rendering to request time], implement [https://wiki.mozilla.org/DXR_Parallel_Tree_Indexing independent tree rendering], or finally [https://bugzilla.mozilla.org/show_bug.cgi?id=959728 replace the config subsystem]
** {{ok|}} Pick newly low-hanging fruit.
*** With the new plugin architecture and Elasticsearch backend, a lot of previously difficult possiblities are opened to us. Examples: index a new language, show result counts, show indexed revision identifiers, do some [https://wiki.mozilla.org/DXR_Result_Mixing result mixing], or default the query parser to interpret text runs as phrase matches.
 
* Release Engineering / Release Operations / Developer Services
** Make try stable and fast.
** Develop automation and self-serve APIs for developers to remove the need to have one full time engineer on buildduty.
** Automate release processes, again to free engineer time and reduce opportunity for error.


====Theme: Operational Efficiency====
====Theme: Operational Efficiency====
Line 152: Line 162:
** Deploy ReviewBoard for developers to start using (carry over from Q3) - platform  
** Deploy ReviewBoard for developers to start using (carry over from Q3) - platform  
** Add support to Bugzilla for the Gmail transition - platform
** Add support to Bugzilla for the Gmail transition - platform
Prototype alternate bug views in Bugzilla to improve performance and usability - platform  
** Prototype alternate bug views in Bugzilla to improve performance and usability - platform  


* QA
* QA
Line 159: Line 169:
** Develop code churn correlation metrics and community health metrics (drop off rates of contributors performing QA tasks). -platform
** Develop code churn correlation metrics and community health metrics (drop off rates of contributors performing QA tasks). -platform


==== A*Team ====
* Release Engineering / Release Operations / Developer Services
 
** Identify, measure, and publish core release engineering KPIs.
(draft only)
** Develop a plan for disaster recovery and business continuation in the event of a disaster for release infrastructure.
 
** Automate merge day processes to free up engineer time and reduce opportunity for error.
Highlights:
* Develop a multi-binary harness for devtools  - desktop
* Add e10s support to Talos, and either Marionette or Mozmill - desktop
* Make end-to-end testing in Autoland possible - platform
* Deploy ReviewBoard for developers to start using (carry over from Q3) - platform
* Add B2G support to mochitest-chrome - fxos
* Add support to Bugzilla for the Gmail transition - platform
* Prototype alternate bug views in Bugzilla to improve performance and usability - platform
* Continue improving sheriff and developer workflows in Treeherder - platform
 
See full list: [[Auto-tools/Goals/2014Q4]]
 
==== QA ====
(Draft)
* Shift focus to exploratory testing and finding bugs rather than verification for non-security bugs to see if that helps us find more high value bugs earlier in the nightly/aurora cycle (Will continue to attempt verification for all security bugs). - desktop
* Consolidate QMO and our dashboards so that it is easier to keep up with the state of quality among all projects - platform
* Experiment with unifying web testing technology stack for MDN with what developers are using to drive better adoption and lower maintenance costs of end to end web automation testing - platform
* Ensure marketplace payments automation running on Firefox 2.0 and above at least once per day fxos/mktplace
* Complete webRTC connection establishment and connection quality automated tests - platform
* Develop code churn correlation metrics and community health metrics (drop off rates of contributors performing QA tasks). -platform
 
[https://wiki.mozilla.org/QA/Goals/2014q4 Full list here]
 
==== Web Engineering ====
'''crash-stats'''
* {{ok|}} begin migrating subsystems to AWS
** e.g. migrate hbase to S3, architect cloud infra, build production-quality AMIs
* {{ok|}} enhance processor flexibility
** e.g. deploy processor2015, enhance tooling for developing post-crash classifiers, prototype alternate processing pipelines
* {{ok|}} enhance search functionality
** e.g. pull users from postgres search so we can shut it off, upgrade ES to 1.x, data dumps of search results
'''elmo'''
* {{ok|}} continue progress towards buildbot retirement
** e.g. migrating diff/compare tools to a10n, migrate remaining buildbot steps to a10n
'''airmo'''
* {{ok|}} prototype self-service publishing
** e.g. getUserMedia-based new hire video recording, user uploads of pictures and videos
 
==== DXR ====
* {{ok|}} Continue improving infrastructure.
** For example: [https://bugzilla.mozilla.org/show_bug.cgi?id=1045183 move file rendering to request time], implement [https://wiki.mozilla.org/DXR_Parallel_Tree_Indexing independent tree rendering], or finally [https://bugzilla.mozilla.org/show_bug.cgi?id=959728 replace the config subsystem]
* {{ok|}} Pick newly low-hanging fruit.
** With the new plugin architecture and Elasticsearch backend, a lot of previously difficult possiblities are opened to us. Examples: index a new language, show result counts, show indexed revision identifiers, do some [https://wiki.mozilla.org/DXR_Result_Mixing result mixing], or default the query parser to interpret text runs as phrase matches.
 
==== SUMO and Input ====
(draft only)
* Implement v1.0 of BuddyUp, the live support app for FirefoxOS, and integrate it with existing SUMO web app.
* Update SUMO forums.
* (Input goals still under discussion)
 
==== Release Engineering / Release Operations / Developer Services ====
* Identify, measure, and publish core release engineering KPIs.
* Develop a plan for disaster recovery and business continuation in the event of a disaster for release infrastructure.
* Make try stable and fast.
* Support Windows 64 initiatives as needed.
* Automate merge day processes to free up engineer time and reduce opportunity for error.
* Develop automation and self-serve APIs for developers to remove the need to have one full time engineer on buildduty.
* Automate release processes, again to free engineer time and reduce opportunity for error.
Smooney
Confirmed users
2,492

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1024756...1024768"