Auto-tools/Projects/2011Q2 Projects: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 38: Line 38:
|-
|-
| Performance Measurements
| Performance Measurements
| Addon Talos Testing
| [[Auto-tools/Projects/AddonStartupPerf|Addon Talos Testing]]
| AMO, Releng, IT
| AMO, Releng, IT
| ??
| ??
Line 46: Line 46:
|-
|-
| Performance Measurements
| Performance Measurements
| Xperf Talos
| [[Auto-tools/Projects/XTalos|Xperf Talos]]
| Perf Team
| Perf Team
| .etl parser, results uploading
| .etl parser, results uploading
Line 65: Line 65:
| IT, cjones
| IT, cjones
| native events, boards
| native events, boards
| {{Pr2}} (1)
| {{Pr2}}
| 60
| 60
| Ctalbert
| Ctalbert
Line 150: Line 150:
|-
|-
| Web Tools
| Web Tools
| SpeedTest UI
| [[Auto-tools/Projects/BugStats|Bug Stats Websites]]
| ??
| RelDrivers
| UX Platform
| UX Platform
| ??
| {{Pr3}}
| ??
| 0
| Mcote
| Mcote
|-
| Web Tools
| Toolbox
| None
| UX Platform
| {{Pr1}}
| 30
| Jhammel
|-
|-
| Automation
| Automation
Line 190: Line 182:
|-
|-
| Automation
| Automation
| Android Support
| [[Ateam/Projects/Uber-crawl|Uber-crawl]]
| Releng, Mobile
| Releng, mobile dev
| {{Pr2}}
| 120
| Jmaher
|-
| Automation
| Uber-crawl
| IT, JS, Metrics, Layout
| IT, JS, Metrics, Layout
| spider, sisyphus
| spider, sisyphus
Line 214: Line 198:
|-
|-
| Tool Infrastructure
| Tool Infrastructure
| Manifest Destiny (landing for xpcshell?)
| [[Auto-tools/Projects/ManifestDestiny|Manifest Destiny (landing for xpcshell?)]]
| N/A
| N/A
| N/A
| N/A
Line 222: Line 206:
|-
|-
| Tool Infrastructure
| Tool Infrastructure
| HTTP Record/Replay
| [[Auto-tools/Projects/HTTP_Record_Replay|HTTP Record/Replay]]
| ??
| ??
| ??
| ??
Line 261: Line 245:
| Ted
| Ted
|}
|}
= Proposed =
= \o/ Completed \o/ =
* <strike>JS Reftest suite</strike>
* <strike>Mozmill 1.4</strike>
* <strike>QA Companion Tool </strike>
* <strike>OOPP test infrastructure and NPAPI test suite creation </strike>
* <strike>[https://wiki.mozilla.org/Auto-tools/Projects/Halreftest GrafxBot</strike>
* <strike>[https://wiki.mozilla.org/Auto-tools/Projects/CrossWeave Crossweave v1</strike>
* <strike>Mozmill 1.5</strike>
* <strike>Android Mochitest, Reftest, Js Reftest, Crashtest, Talos</strike>
* <strike>Bug Hunter Initial Rollout</strike>
* <strike>[https://wiki.mozilla.org/Auto-tools/Projects/FennecPT Fennec Profile Manager]</strike>
* <strike>[https://wiki.mozilla.org/Auto-tools/Projects/ProfileManager Desktop Profile Manager Replacement]</strike>
* <strike>SpeedTest v1 Framework</strike>
* <strike>[http://brasstacks.mozilla.com/toolbox Toolbox]</strike>

Latest revision as of 00:52, 14 June 2011

Automation and Tools Planning Q2

Our projects can be broken up as follows:

  • Performance - Projects surrounding measurement of performance
  • Web Tools - Projects to build web tools and web UIs for automation frameworks
  • Automation - Projects to automate some thing or create automation frameworks
  • Tool Infrastructure - Tool "building blocks" from which we can make other tools

Please fill out this table with your best estimates for the projects you are involved in. An explanation of the fields:

  • Area - one of the four project areas
  • Project Name - the project name, and should be a wiki link to a project details page at Auto-tools/Projects/<projectname> (See Project Foo below for an example)
  • Team Deps - Teams you will need to work with/depend on to drive this project
  • Project Deps - Pieces of Tool infrastructure your project depends on
  • Priority - the priority of this project in terms of this quarter
  • Size - Size of project in hours - include total here, put the breakdown on your details page
  • Owner - The one (or rarely, two) people that own this project.

If you would like a sample details page to work from, feel free to use Project Foo for a template.

The Projects

Area Project Team Deps Project Deps Priority Size (hrs) Primary Owner
Performance Measurements User Responsiveness None native events P1 ?? Ted
Performance Measurements Addon Talos Testing AMO, Releng, IT ?? P1 ?? Anode
Performance Measurements Xperf Talos Perf Team .etl parser, results uploading P2 30 Jmaher
Performance Measurements Other Perf Measures Perf Team Xperf talos P3 50 Jmaher
Performance Measurements Eideticker IT, cjones native events, boards P2 60 Ctalbert
Performance Measurements Speed Test Framework IT (for machine installations) None (but might benefit from UX Platform) ?? 40-64 Mcote
Web Tools Bugzilla REST API ?? ?? ?? ?? Dkl
Web Tools Bugzilla Pulse & Tool Integration IT, Pulse ?? Glob
Web Tools Updated Guided Bug Entry P2 30 Glob
Web Tools "Instant" Quick Search IT, Metrics P3 Unknown Glob
Web Tools HG Improvements ?? ?? ?? ?? (contractor)
Web Tools TCM (Litmus 2) ?? ?? ?? ?? (contractor)
Web Tools AutoLog None UX Platform P1 240 Jgriffin
Web Tools WOO Metrics UX Platform P1 120 Jgriffin
Web Tools Bug Hunter UI ?? UX Platform ?? ?? Bc/Mcote
Web Tools Bug Stats Websites RelDrivers UX Platform P3 0 Mcote
Automation Bug Hunter Framework IT spider, sisyphus ?? ?? Bc
Automation Mozmill 2.0 RelEng native events ?? ?? Ctalbert
Automation Crossweave 2 Services Mozmill (mozprofile, mozrunner) P2 160 Jgriffin
Automation Uber-crawl IT, JS, Metrics, Layout spider, sisyphus ?? ?? Bc
Automation Harnesses that need Servers RelEng, F1, Sync, Firebug, Safe Browsing, Identity, Security, Apps Mozharness, Autolog ?? ?? ??
Tool Infrastructure Manifest Destiny (landing for xpcshell?) N/A N/A P2 20 Jhammel/Jmaher
Tool Infrastructure HTTP Record/Replay ?? ?? ?? ?? ??
Tool Infrastructure Native Events ?? ?? ?? ?? Ahal
Tool Infrastructure MozBase RelEng Mozmill (mozprocess, mozprofile, logging), automation.py P2 160 Jmaher
Tool Infrastructure Web UX Platform IT None, but benefits from existing web projects ?? 80-120 Mcote
Tool Infrastructure SpecialPowers Developers Most test harnesses P1 ?? Ted

Proposed

\o/ Completed \o/