MozillaWiki - User contributions [en]

Auto-tools/Meetings/2012-07-30

2017-04-19T21:59:07Z

Arich:

== Goals Progress ==

Below are our [https://wiki.mozilla.org/Auto-tools/Goals/2012Q3 top level goals]. Beneath each goal, note any progress made towards that goal this week.
* {{ok|Support the B2G and platform team by moving existing automation to that platform as well as expanding automation on B2G and B2G devices for basecamp deliverables.}}
** [mihneadb] SUTAgentC working on B2G. Some tests passing.
** [mihneadb] SUTAgent tests (passing for the Java implementation) in mozbase/mozdevice. {{bug|778366}}
** [ahal] reftests running consistently on desktop-linux-emulator (note: consistently != passing) {{bug|773482}}
** [mcote] [[Auto-tools/Projects/SUTAgent|SUTAgent requirements spec]] nearly done. AutoPhone adb -> SUT awaiting review ({{bug|776737}}).
* {{ok|Expand Mobile testing platforms for B2G and Fennec Native to include user devices, NEON Chipsets (panda boards), and ARMv6 (Beagle boards).}}
** [wlach] experimenting with his new ARMv6 tablet (unfortuantely the wrong model was ordered, so no HDMI out, but may still be possible to do some basic tests of checkerboarding through internal browser metrics).
* {{ok|Establish new Datazilla system as a useful tool for capturing and diagnosing talos performance regressions on a per-push basis, as well as capturing data for network and B2G performance tests.}}
** ''NOTE:'' This is largely a change to the data harvesting and analysis side of the Talos system (even though some changes are required to the test harness and tests themselves). We will '''not''' be replacing existing Talos data harvesting system in Q3. By the end of Q3, we want to have the new performance data harvesting and analysis system Datazilla to a point at which it can shadow the old system and we can use Q4 to verify that the new approach captures just as many regressions as the old system does. Potential timeframe for conversion of the old system to the new Datazilla system is in Q1 2013 (earliest "thumb in the wind" estimate).
* {{ok|Upgrade BMO to 4.2, deploy tracking flags optimizations, UX improvements (comment tagging, mid-air resolution)}}
** lots of search work for the bmo/4.2 blocker {{bug|677757}}
* {{ok|Make TBPL More Orange aware to make it easier to file intermittent orange bugs, and so that we can more adequately track (and therefore address) issues around android-related and memory leak intermittent failures}}
** [edmorley] Filed {{bug|778688}} for making TBPL handle more types of failures (to reduce need for manual starring / the need to open full logs) and started collating issues under it.
* {{ok|Enable QA and contributors to increase their skills and participation by crafting automated tests for B2G and desktop smoketests by providing examples, mentoring, and documentation}}

[https://www.pivotaltracker.com/projects/582883# '''Check out Pivotal Tracker''']

== Highlights ==

''This is a place for people to put announcements or to describe activities that they'd like to highlight. It's not the responsibility of the MC to find things to put here.''
* [DBurns] The Browser Automation Spec [http://dvcs.w3.org/hg/webdriver-test test repo] has been created and [https://github.com/AutomatedTester/W3-BrowserAutomation-tests mirrored] on github if people want to follow

== In-Depth Project Discussion ==

Retrying wlach on Eideticker.

== The Overview ==

''Progress, notes, problems, and other statuses about current projects. Add any new projects to this template!''

=== [[Auto-tools/Projects/AutoPhone|AutoPhone/Noah's Ark]] ===
* [mihneadb] In case you need an account for installing stuff (example: ROM Manager for installing CWM easily) on Android (auto)phones: user: mozautophone@gmail.com, passwd: ***** (It is a dummy account, has no data.)
* [mcote] Finishing up proper requirements spec for SUTAgent: [[Auto-tools/Projects/SUTAgent]]
* [mcote] AutoPhone adb -> SUT transition finished and up for review.

=== [[Auto-tools/Projects/Bughunter|Bughunter]] ===

=== [[BMO|Bugzilla]] ===
* pushed changes: http://globau.wordpress.com/2012/07/26/happy-bmo-push-day-6/
* [glob] service-now tweaks for various forms
* [glob+dkl] discovered security issue (glob), patched (lpsolit), and drove upstream release (dkl)
* [glob] lots of search work for the bmo/4.2 blocker
* [dkl+glob] large amounts of upstream reviews and commits due to lpsolit's return from holiday
* [dkl+glob] bmo administration work

=== [[Project_Eideticker|Eideticker]] ===
* [mdas] video capture is working for b2g pandaboards; now adding eideticker framework support
* [wlach] - eideticker seems to have identified a mobile regression in {{bug|777357}}, investigating further

=== [https://github.com/mozilla/Firebug-Test-Runner Firebug Testing] ===

=== [[Auto-tools/Projects/Jetperf|Jetperf]] ===

=== [[Auto-tools/Projects/Marionette|Marionette]] ===
* [DBurns] stabilising a test for Marionette
* [DBurns] Aligning some more methods with Selenium

=== Mobile Automation ===
* [wlach] / [jmaher]: Looking into underlying causes of rebooting tegras (we think we've isolated it to the behaviour of the watcher). See {{bug|771626}}
* [wlach] / [jmaher] Lots of related work to the agent and watcher to be more debuggable

=== [[Auto-tools/Projects/Mobile_Evangelism_Site_Scraper|Mobile Evangelism Site-Scraping Tool]] ===

=== Mochitest ===

=== [[Auto-tools/Projects/MozBase|MozBase]] ===
* [mihneadb] Small fixes to devicemanagerSUT {{bug|778329}} {{bug|778363}}
* [mihneadb] Mozbase/moztest (results) - getting closer to first "release" {{bug|774419}}
* [ahal] fixed regression in mozprocess {{bug|776931}}
** updated tests + other minor work around mozbase

=== [[Auto-tools/Projects/Mozmill|Mozmill]] ===
* [hskupin] [https://groups.google.com/forum/?fromgroups#!topic/mozmill-dev/Y5-N6mlWOBw Released Mozmill 1.5.17] with a fix for HTTPd issues

=== [[Auto-tools/Projects/MozTrap|MozTrap]] ===

=== [[Auto-tools/Projects/Datazilla|New Graphserver (Datazilla)]] ===
* [jeads] Some progress from netops on setting up firewall holes for datazilla {{bug|778447}}
* [jeads] Working on implementing t-test schema and push log walking for new talos metrics implementation.
* [camd] Wrote a management command to verify JSON data blobs and report which build / branch any error blogs come from. Used this command to confirm the assertion that bad talos JSON data was only from 14.01 and before.

=== [[Auto-tools/Projects/Open_Web_Apps_Testing|Open Web Apps]] ===

=== [[Auto-tools/Projects/peptest|Peptest]] ===
* [ahal] trying to get peptest test using talos sites up and running, but keep getting blocked by mozbase regressions

=== [[Auto-tools/Projects/Powerball|Powerball]] ===

=== [[Auto-tools/Projects/Pulse|Pulse]] ===

=== [[Auto-tools/Projects/Signal_From_Noise|Signal From Noise]] ===

=== [[Auto-tools/Projects/Speedtests|Speedtests]] ===
* vlad apparently got SpeedTests [http://hg.mozilla.org/users/vladimir_pobox.com/speedtests/ working on Android]! (via adb, but still...)

=== Systems ===

=== Talos ===
* [jhammel] chart of buildbot:TBPL:talos:graphserver mapping http://k0s.org/mozilla/talos/talosnames.html
** accurate, though incomplete: http://k0s.org/mozilla/blog/20120724135349

=== Sheriffing & Trees ===
* [edmorley] Day-to-day sheriffing of the trees.
* [edmorley] Sheriffing issues of note:
** Philor away 15th July-5th Aug.
** Tracking down PGO build failures on Windows ({{bug|776503}}).
** {{bug|777634}} - Unable to access TBPL build summaries and logs.
** Discussions about Try hg issue.
** Dealing with fallout from accidental Try repo reset.
** Pymake bustage on trunk ({{bug|776878}}).
** {{bug|777273}} - Only ~50 tegras are running tests; tegra pending test job count is at 1600 and rising.
** {{bug|777436}} - Ascertain which Android test suites have >30% failure rate and hide them.
** Spent an entire day resolving overlapping bustage of win crashes + m-oth leaks + two separate Android XUL R3 failures :-(
* [edmorley] Misc sherrifing papercuts filed/followed up: https://bugzil.la/776467,762710
* [edmorley] Fixed:
** {{bug|774649}} - Make the 'base' link on the file revisions page link to the former file's revision log, not file view, to save time when sheriffing/filing.
** {{bug|766952}} - Remove empty <span>s and switch per element styles to style-gitweb.css, to improve browser memory usage/rendering performance on large diffs (reduces memory usage from 1,132 MB to 784 MB). Often hit this issue when sheriffing.
** {{bug|772419}} - Disable Qt+rpm builds to save load.
* [edmorley] Started using a new [sheriff-want] whiteboard annotation to keep track of bugs across product/releng/testing/TBPL that will make sheriff's lives easier: https://bugzil.la/sw:sheriff-want

=== [https://treestatus.mozilla.org/ Treestatus] ===

=== [https://tbpl.mozilla.org/ Tinderboxpushlog] ===
* [edmorley] Reviewed:
** {{bug|776692}} - next-/prev-unstarred shortcuts have wrong order when a starred result is selected.
** {{bug|777673}} - next-/prev-unstarred shortcuts skip a failure after starring twice with onlyunstarred=1.
* [edmorley] Landed {{bug|703967}} - Add indexes to endtime/buildername in the runs/builders tables, to speed up data expiration in production.
* [edmorley] TBPL production update ({{bug|777105}}).
* [edmorley] Discussions with devs about TBPL feature requests: https://bugzil.la/778231,778390
* [edmorley] Created a meta bug for making TBPL handle more types of failures (to reduce need for manual starring / the need to open full logs) and started collating bugs under it ({{bug|778688}}).

=== [[Auto-tools/Projects/WarOnOrange|War on Orange]] ===
* [edmorley,jgriffin] {{bug|776932}} - Indicators for which top-oranges are resolved fixed are broken.
* [edmorley] More CCing of devs and pinging for top oranges on trunk, aurora and beta.
* [edmorley] Backported more intermittent orange fixes: https://bugzil.la/770456,558220
* [edmorley] {{bug|776945}} - Update in-tree copies of mozmill to pick up bug 558220's httpd.js [orange] fix.
* [edmorley] Fixed {{bug|778433}} - Raise ShutdownLeakLogger's MAX_LEAK_COUNT to something less annoying, until bug 728294 lands.

=== Web QA ===
* [dhunt] [http://blargon7.com/2012/07/flynnid-0-2/ Released FlynnID 0.2] with the new feature of using configuration files
* [dhunt] [http://blargon7.com/2012/07/bidpom-drops-support-for-selenium-rc/ Dropped support for Selenium RC API in Browser ID Page Object Model]
* [dhunt] Transferred BIDPOM to main Mozilla github repository

=== Automation Development ===

== Upcoming Events ==

''All times Pacific Time, click on link to find your timezone''
* Platform Meeting (all platform engineers) [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120731T11&p1=283 Tuesday at 11 AM], Conf # 8605.
* Mobile Test Automation [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120801T1030&p1=283 Wednesday at 10:30 AM], Vidyo Warp Core
* Mozharness [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120801T1300&p1=283 Wednesday at 1 PM], Vidyo Warp Core
* Marionette/Eideticker Meeting [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120802T10&p1=283 Thursday at 10 AM] Conf # 304
* Signal from Noise [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120802T1100&p1=283 Thursday at 11 AM] #343

== Round Table ==

* As announced in IRC last week, jhammel and wlach are now the official owners of mozbase.
* Datazilla attempted to land in production, unclear whether or not we did. Ctalbert and Jeads to follow up with IT

=== Holidays and Trips ===
* Next Monday holiday in Toronto
* Carljm is out all week.
* Whimboo is out all week.

=== Next week MC ===
* Jhammel mc
* davehunt on how we use Selenium

== Misc ==
* Friday was [http://sysadminday.com/ SysAdmin Appreciation Day].
* From [http://www.brianbondy.com/blog/id/147/ User study on mentoring a large first bug]: "Bugzilla was easy to use and straightforward as well"

DeveloperServices

2016-04-14T19:56:44Z

Arich: updated info for team lead, removed projects section

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git, and svn.
* We support the try repository.
* We also provide operational support for BMO, MozReview, Treeherder, MXR, and DXR.
}}<section end=summary />

= Oncall for VCS =
"Oncall" is really "escalation path" for services we handle. Start with the service owner, then irc channel (below), then escalate to oncall if no response.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Hal Wine
| hwine
|-
| Backup on call
| Kendall Libby
| fubar
|-
| Escalation
| Amy Rich
| arr
|}
As always with service issues, please indicate urgency and contact information in any page or voice mail. Using Nagios paging is most reliable. For less urgent contact methods, see [[#contact|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|BMO, Treeherder, Reviewboard, DXR, MXR, hg, git
|ET
|-
|Gregory Szorc
|gps
|San Francisco, CA, USA
|hg, Reviewboard, build module owner
|PT
|-
|Hal Wine (on loan from RelEng)
|hwine
|San Francisco, CA, USA
|VCSs, releng and IT liaison
|PT
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #vcs].

Additional folks work on various modifications and extensions to the version control systems. They can be reached at dev-version-control@lists.mozilla.org or [ircs://irc.mozilla.org/#vcs #vcs].

The other systems we support follow the "devops" model -- the first point of contact for operations and support are the following channels on irc:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR
* There is no help to be found for MXR. Abandon all hope, etc, etc.

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

ReleaseEngineering/Slave Naming

2015-08-04T22:36:13Z

Arich:

= Introduction =
At Release Engineering we do builds and tests of Firefox, Firefox for Android, Firefox OS and Thunderbird. We also do some other tier-2 type of jobs on the same hardware used to ship the mentioned products.
For builds, we build both on real hardware and VMs (in-house & AWS).
For unit and performance tests (aka talos), we build both on real desktop machines, VMs (EC2) and mobile development boards (tegras & pandas).
As we move everything to scl3, we can see the purpose of the machine indicated on the full hostname (try build machines VS release build machines VS test machines VS "Windows" vlan).

== Notes ==
* We only use "try" or "y" for ec2 instances since renaming is harder with in-house hosts
* We are unable to use hostnames longer than 15 characters on Windows, so any try hosts in EC2 are y-2008, not try-2008.
* Moving machines from the try vlan to the build vlan will requires hostname changes (after the first 'dot').

= Proposed naming =
== Server hostname convention ==
P-O-T-XXXX

1) P = purpose
* "b-" - for build machines
* "t-" - for test machines
* "y-" - for try machines in AWS
<br />
2) O = OS + instruction size (optional)
* xp32/w732/w864/w1064/2008/2012
** we currently use "w64" for "w2008"
* linux32/linux64
** for linux we camouflage the distro
* snow/lion/mtnlion/mavericks/yosemite

3) T = Type of hardware
<br />
For VMs:
* "ec2" for Amazon on-demand instances
* "spot" for Amazon spot instances
* "vmw" for in-house vmware
<br />
For real hardware:
* "ix" for ix machines
* "r#" - # depends on the revision of Mac mini that we use
<br />
4) XXXX = number (or XXX = number in AWS)
<br />
Fixed digits allow lexical sorting, but limit to 9999 slaves per type. This is at variance with numbering throughout the rest of Mozilla, where zero-padding is not used.

=== Examples ===
Build machine examples:
* b-2008-spot-XXX (15 chars)
* b-2008-ix-XXXX (14 chars)
* b-lion-r#-XXXX
<br />
Try machine examples:
* y-2008-spot-XXX (15 chars)
* y-linux64-spot-XXXX
* y-linux32-spot-XXXX
<br />
Test machine examples:
* t-linux32-spot-XXXX
* t-linux64-spot-XXXX
* t-linux32-ix-XXXX
* t-linux64-ix-XXXX
* t-snow-r4-XXXX
* t-yosemite-r5-XXXX
* t-xp32-ix-XXXX
* t-w732-ix-XXXX
* t-w864-ix-XXXX
* t-w1064-ix-XXXX

== Mobile hostname convention ==
T-XXXX

T = type (e.g. panda)
Examples:
* panda-XXXX

== Other infra ==
buildbot-masterXX - for buildbot masters
foopyXXX - for foopy machines

= Current naming differences =
NOTE: Differences are bolded to make it easier to read
As of January, 2014 (note that machines have moved to four digits)
{| border="1" cellpadding="2"
! Proposed
! Current
|-
| b-linux64-spot-XXXX
| b'''ld'''-linux64-spot-XXX
|-
| y-linux64-spot-XXXX
| '''tr'''y-linux64-xpot-XXXX
|-
| y-linux32-spot-XXXX
| '''tr'''y-linux32-xpot-XXXX
|-
| b-2008-ix-XXXX
|
|-
| b-2008-spot-XXX
|
|-
| y-2008-spot-XXX
|
|-
| b-lion-r#-XXXX
| b'''ld'''-lion-r#-XXX
|-
| t-linux32-spot-XXXX
| t'''st'''-linux32-spot-XXX
|-
| t-linux64-spot-XXXX
| t'''st'''-linux64-spot-XXX
|-
| t-linux32-ix-XXXX
| talos-linux32-ix-XXX
|-
| t-linux64-ix-XXXX
| talos-linux64-ix-XXX
|-
| t-snow-r4-XXXX
| talos-r4-snow-XXX
|-
| t-mtnlion-r5-XXXX
| talos-mtnlion-r5-XXX
|-
| t-yosemite-r5-XXXX
|
|-
| t-xp32-ix-XXXX
| t-xp32-ix-XXX
|-
| t-w732-ix-XXXX
| t-w732-ix-XXX
|-
| t-w864-ix-XXXX
| t-w864-ix-XXX
|}

ReleaseEngineering/Slave Naming

2015-08-04T16:31:34Z

Arich: remove a bunch of outdated information and update for use of y- for try.

= Introduction =
At Release Engineering we do builds and tests of Firefox, Firefox for Android, Firefox OS and Thunderbird. We also do some other tier-2 type of jobs on the same hardware used to ship the mentioned products.
For builds, we build both on real hardware and VMs (in-house & AWS).
For unit and performance tests (aka talos), we build both on real desktop machines, VMs (EC2) and mobile development boards (tegras & pandas).
As we move everything to scl3, we can see the purpose of the machine indicated on the full hostname (try build machines VS release build machines VS test machines VS "Windows" vlan).

== Notes ==
* We only use "try" or "y" for ec2 instances since renaming is harder with in-house hosts
* We are unable to use hostnames longer than 15 characters on Windows, so any try hosts in EC2 are y-2008, not try-2008.
* Moving machines from the try vlan to the build vlan will requires hostname changes (after the first 'dot').

= Proposed naming =
== Server hostname convention ==
P-O-T-XXXX

1) P = purpose
* "b-" - for build machines
* "t-" - for test machines
* "y-" - for try machines in AWS
<br />
2) O = OS + instruction size (optional)
* xp32/w732/w864/w1064/2008/2012
** we currently use "w64" for "w2008"
* linux32/linux64
** for linux we camouflage the distro
* snow/lion/mtnlion/mavericks/yosemite

3) T = Type of hardware
<br />
For VMs:
* "ec2" for Amazon on-demand instances
* "spot" for Amazon spot instances
* "vmw" for in-house vmware
<br />
For real hardware:
* "ix" for ix machines
* "r#" - # depends on the revision of Mac mini that we use
<br />
4) XXXX = number (or XXX = number in AWS)
<br />
Fixed digits allow lexical sorting, but limit to 9999 slaves per type. This is at variance with numbering throughout the rest of Mozilla, where zero-padding is not used.

=== Examples ===
Build machine examples:
* b-2008-spot-XXX (15 chars)
* b-2008-ix-XXXX (14 chars)
* b-lion-r#-XXXX
<br />
Try machine examples:
* y-2008-spot-XXX (15 chars)
* y-linux64-spot-XXXX
* y-linux32-spot-XXXX
<br />
Test machine examples:
* t-linux32-spot-XXXX
* t-linux64-spot-XXXX
* t-linux32-ix-XXXX
* t-linux64-ix-XXXX
* t-snow-r4-XXXX
* t-yosemite-r5-XXXX
* t-xp32-ix-XXXX
* t-w732-ix-XXXX
* t-w864-ix-XXXX
* t-w1064-ix-XXXX

== Mobile hostname convention ==
T-XXXX

T = type (e.g. panda)
Examples:
* panda-XXXX

== Other infra ==
buildbot-masterXX - for buildbot masters
foopyXXX - for foopy machines

= Current naming differences =
NOTE: Differences are bolded to make it easier to read
As of January, 2014 (note that machines have moved to four digits)
{| border="1" cellpadding="2"
! Proposed
! Current
|-
| b-linux64-spot-XXXX
| b'''ld'''-linux64-spot-XXX
|-
| y-linxu64-spot-XXXX
| '''tr'''y-linux64-xpot-XXXX
|-
| y-linxu32-spot-XXXX
| '''tr'''y-linux32-xpot-XXXX
|-
| b-2008-ix-XXXX
|
|-
| b-2008-spot-XXX
|
|-
| y-2008-spot-XXX
|
|-
| b-lion-r#-XXXX
| b'''ld'''-lion-r#-XXX
|-
| t-linux32-spot-XXXX
| t'''st'''-linux32-spot-XXX
|-
| t-linux64-spot-XXXX
| t'''st'''-linux64-spot-XXX
|-
| t-linux32-ix-XXXX
| talos-linux32-ix-XXX
|-
| t-linux64-ix-XXXX
| talos-linux64-ix-XXX
|-
| t-snow-r4-XXXX
| talos-r4-snow-XXX
|-
| t-mtnlion-r5-XXXX
| talos-mtnlion-r5-XXX
|-
| t-yosemite-r5-XXXX
|
|-
| t-xp32-ix-XXXX
| t-xp32-ix-XXX
|-
| t-w732-ix-XXXX
| t-w732-ix-XXX
|-
| t-w864-ix-XXXX
| t-w864-ix-XXX
|}

ReleaseEngineering/How To/Process release email

2015-04-17T17:47:26Z

Arich: added detail about sns notifications

{{Release Engineering How To|Process email to release@}}
This is a list of automatically generated emails you should expect to receive as a release engineer at mozilla. It is not complete.

Note that email is not a good notification methodology, and better systems should always be preferred. However, it often is all that is available for audience which needs the notification. To minimize the pain of email notifications, follow these guidelines:
* email should go to a unique address for the service. This can be achieved by using "plus addresses" (preferred due to positive filtering criterea).
** if not possible, the message MUST have a unique start to the subject field (brittle).
* email should be documented on this page.

= Index =
Zimbra glob/wildcard syntax, in alpha order by field then match string

{| cellpadding="10" cellspacing="0" border="1" class="fullwidth-table sortable"
!Field !! Wildcard !! Further Notes
|-
|Subject || collapse report || [[#Performance Metrics]]
|-
|Subject || Suspected machine issue (* || Not an actionable email at this point. (from: nobody@cruncher - s/a {{bug|825625}}
|-
|Subject ||Talos Suspected machine issue *|| ''if you don't know, you don't care''
|-
|Subject ||Try submission *||to: autolanduser@mozilla.com
|-
|Subject ||[vcs2vcs] alert_major_errors* || '''major processing error''' make sure build duty and/or hwine know [[#vcs2vcs|details]]
|-
|Subject ||[vcs2vcs]: git.m.o push N failed: * || single occurrence related to git.m.o/releases/gecko.git '''if repeated, this is a major processing error''' make sure build duty and/or hwine know [[#vcs2vcs|details]]
|-
|Subject ||[vcs2vcs] process delays* || '''if repeated, this is a major processing error''' make sure build duty and/or hwine know [[#vcs2vcs|details]]
|-
|Subject || [release-runner] failed || [[#What_to_do_when_one_is_received_6| How to investigate release runner failures]]. ''(ignore if a release isn't actively being started)''
|-
|To || release+aws@mozilla.com || AWS admin email, service notifications & marketing. See [[#Amazon_EC2_Instance_scheduled_for_retirement|list of AWS emails]], contact catlee if unsure how to handle.
|-
|To || release+bitbucket@mozilla.com || Mozilla Bitbucket Admin email (contact hwine for now)
|-
|To || release+vcs2vcs@mozilla.com || Output from vcs2vcs hg<->git conversion ([[#vcs2vcs|details]])
|-
|To || release+aws-sanity-check@mozilla.com || Output from cruncher [http://hg.mozilla.org/build/cloud-tools/file/default/aws/aws_sanity_checker.py aws_sanity_checker.py] (contact rail)
|-
|To || release+ec2.*@mozilla.com || error output from crontab on the indicated machine. FIX ISSUE!
|-
|To || release+sns@mozilla.com || SNS issue notifications from various services. FIX ISSUE!
|-
|To || release+update.b2g.o@mozilla.com || low disk space on dogfood update server, see {{bug|877224}}
|-
|To || release+chromecast@mozilla.com || Developer account for Chromecast app support {{bug|1037018}} ([[#chromecast|details]])
|}

<br />

__TOC__

=Performance Metrics=
== Why we get them ==
We get various emails containing raw data that relates to a performance bottle neck at some point in time. Typically these are produced by cron jobs, and so received regularly regardless of metric status. (I.e. they may not require any action.)

== What is sending them ==
Since this is a "catch all" category, various tools send them. Check the full headers for information on sender and source machine as needed.

== What to do when one is received ==
If you don't know what it's about, you don't need to deal with it beyond setting up a filter to ignore it.

== How to silence or acknowledge this alert ==
It's not an alert, so they'll keep coming until the end of time. Filter them if you're not involved with them.

== Future plans ==
Adhoc, so varies by email. Theoretically, these ''should'' be transitional, and moved into automation and alerting as soon as the metric is understood.

== How to best filter these emails ==
Since these are adhoc, you'll need adhoc filters. It would be nice if folks used a common prefix on subjects, such as "<tt><nowiki>[releng metrics]</nowiki></tt>".

<div id="vcs2vcs"> </div>
= vcs2vcs System=
== Why we get them ==
These emails are the interim notification for vcs2vcs system, and indicate an error that must be addressed. The b2g project is dependent upon parts of the vcs2vcs system, as are other developers and partners.

== What is sending them ==
All emails are sent (perhaps indirectly) by a script from [http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/ vcs2vcs tools]. The hosts sending the email will be one of the ones listed in [http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/file/default/status the configs]. Full details of how each script is run, including trouble shooting tips, are in the [http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/file/default/docs docs] (a formatted copy ''may'' be online [http://people.mozilla.com/~hwine/tmp/vcs2vcs/ here]).

== What to do when one is received ==
* if the subject contains "[vcs2vcs] AUTOFIX process delays", then look for another email within a few minutes and proceed as follows:
** if a second email from the same host follows almost immediately with a subject of "[vcs2vcs] process delays", then the AUTOFIX failed, which is an unexpected condition. Page hwine.
** if no followup email is received, the AUTOFIX worked. Log in {{bug|829025}} & delete (or just delete and leave for hwine to log).
* if the subject contains "[vcs2vcs] process delays" '''''and''''' is repeated every 20 minutes, this is a service outage - one or more repositories are no longer being updated. The email contents will give specific errors. Consult the trouble shooting section of the docs (above) for guidance and/or PAGE hwine.
** Unfortunately, there appear to be a few race conditions between scripts, so a single occurrence of the email may be a false positive. ({{bug|839595}} filed to track this.)

* if the subject contains "[vcs2vcs] alert_major_errors alert", this is a major problem - one or more repositories are no longer being updated. The email contents will give specific errors. Consult the trouble shooting section of the docs (above) for guidance and/or contact hwine.
** The most common cause of this is hg repo corruption, the recovery is scripted, but can take some time. Please add to {{bug|808129}} if you fix, or block that bug with a new bug.
** NOTE: you may receive an additional email after the root cause is resolved. (The alert checks on the hour for problems in the prior hour.)

* if the subject containes "[vcs2vcs]: git.m.o push N failed for gecko.git:", this is a (usually) transient problem with pushing gecko.git (the partner facing gecko repository) to either git.m.o or git staging. Two pushes are tried each iteration - both should succeed. Each push is numbered '1' or '2', if you see only one email report, the other already succeeded, and is ignorable. One or two sets of emails is ignorable, any more needs investigation, starting with the health of git.mozilla.org. (Note that the message is short, as this also pages hwine via sms, where brevity is nice.)

* if the subject is something else, this is likely unexpected output from a cron job. Judge the severity and escalate to hwine appropriately. File a bug to get better diagnosis of this error condition in the future.

== How to silence or acknowledge this alert ==
Resolving the root cause will stop the emails.

== Future plans ==
The system will eventually be transitioned to IT for operations. Specific email will be converted to nagios alerts before then.

== How to best filter these emails ==
All of these emails are sent to the addresses of the form: <tt>release+vcs2vcs*@mozilla.com</tt>. Common sub addresses are:
; release+vcs2vcs : mail that will have specifics in the Subject line.
; release+vcs2vcs+forward : mail to vcs2vcs user, forwarded via <tt>~/.forward</tt> file.

= Release runner =
== Why we get them ==
Release runner sends e-mail when it fails in any way. Eg, failing to poll ship it after a long period of time or failing to start a submitted release.

== What is sending them ==
* Source: https://hg.mozilla.org/build/tools/file/default/buildfarm/release
* Sent by: buildbot
* Runs on: buildbot-master36 through supervisord

== What to do when one is received ==
[[Release:Release_Automation_on_Mercurial:Troubleshooting#How_to_investigate_release_runner_failures | How to invesigate release runner failures]]

== How to silence or acknowledge this alert ==
Fix whatever problem release runner has hit. (Sometimes this means waiting out network issues.) There's no way to ack (in the nagios sense) release runner e-mails.

== Future plans ==
They're here to stay.

== How to best filter these emails ==
[release-runner] in the subject.

=Amazon EC2 Instance scheduled for retirement=
==Example==
One or more of your Amazon EC2 instances in the us-east-1 region is scheduled for retirement. The following instance(s) will be shut down after 12:00 AM UTC on 2013-10-22.

i-02cc2669

== Why we get them ==
Amazon needs us to move our virtual instance(s) off of certain physical hardware so they can perform maintenance on it.

== What is sending them ==
Automated notification sent by no-reply-aws@amazon.com

== What to do when one is received ==
* determine what host is running on the specified EC2 instance.
* power the instance down in an orderly manner
* start it back up

== How to silence or acknowledge this alert ==

== Future plans ==

== How to best filter these emails ==
Filter on the sender and subject line.

=SNS Notifications from AWS=
==Example==
Anything with the Subject "AWS Notification Message"

== Why we get them ==
We use SNS to deliver notifications about various Amazon services as well as services like Papertrail. These are generally critical alerts that we've set up and should be dealt with/investigated in a timely fashion. At the moment, only AWS Cloudwatch and Papertrail use this service, but we will likely add more in the future after we get an SNS->irc bot set up because it allows for an easy HTTP/HTTPS endpoint push that other services already integrate with.

== What is sending them ==
The Amazon SNS service notification topic "buildduty"
* arn:aws:sns:us-west-2:314336048151:buildduty
* arn:aws:sns:us-east-1:314336048151:buildduty

== What to do when one is received ==
Determine what the issue is by parsing the output. Make sure someone is working on fixing the issue (if you're not sure how, at least contact buildduty for their input/advice).

== How to silence or acknowledge this alert ==
Fix the underlying issue to stop the alert.

== Future plans ==
In the near future we intend to send SNS notifications to an irc bot instead of via email.

== How to best filter these emails ==
Ideally you should not filter them except into a high priority folder. You can filter on the Subject or the To address.

<div id="chromecast"></div>

= Mail to release+chromecast@mozilla.com =
== Why we get them ==
The mobile team is adding Chromecast support (ability to fling videos/tabs from a device to a TV). They need a persistent account not linked to a single developer who might leave the company at some point.

== What is sending them ==
These emails come from the

== What to do when one is received ==
Traffic should be light. If the email is not simply Google self-promotion, please forward it to lead mobile devs, namely :blassey and :mfinkle.

== How to silence or acknowledge this alert ==

== Future plans ==

== How to best filter these emails ==
You can either filter on the "To:" field for "release+chromecast@mozilla.com" to catch just these emails, or filter on "From:" for "noreply@google.com" and move all mail from Google (we have multiple accounts mailing us intermittently) to a separate Google subfolder (coop).

<hr />
<small>

=Sample=
== Why we get them ==
Give a brief explanation of why this email is for, what it helps us do and why it should be watched

== What is sending them ==
Include a link to the source of the program sending the email. Include information on which hosts are sending the email, and give information on how program runs. Is it a daemon? Does it have an init script? Do you run it under screen?

== What to do when one is received ==
* if the title contains "[scl-production-puppet-new] <slavename> is waiting to be signed", this is for information and requires no immediate action
* if the title contains "[scl-production-puppet-new] <slavename> has invalid cert", the script will try once to clean the cert before sending the email. If this is successful, you'll see a matching "<slavename> is waiting to be signed" email. The key will be automatically signed

== How to silence or acknowledge this alert ==
Include information on how to make the emails stop

== Future plans ==
provide any future plans for this email. Is it temporary? Is it going to be replaced by a real dashboard? Are you going to add/change things people filter on?

== How to best filter these emails ==
provide insight on how to filter these emails. Is there a distinguishing header? Is it always from a specifc host, or family of hosts? Is there a distinctive subject?
</small>

ReleaseEngineering/How To/Process release email

2015-04-17T17:31:33Z

Arich: added sns plussed address

{{Release Engineering How To|Process email to release@}}
This is a list of automatically generated emails you should expect to receive as a release engineer at mozilla. It is not complete.

Note that email is not a good notification methodology, and better systems should always be preferred. However, it often is all that is available for audience which needs the notification. To minimize the pain of email notifications, follow these guidelines:
* email should go to a unique address for the service. This can be achieved by using "plus addresses" (preferred due to positive filtering criterea).
** if not possible, the message MUST have a unique start to the subject field (brittle).
* email should be documented on this page.

= Index =
Zimbra glob/wildcard syntax, in alpha order by field then match string

{| cellpadding="10" cellspacing="0" border="1" class="fullwidth-table sortable"
!Field !! Wildcard !! Further Notes
|-
|Subject || collapse report || [[#Performance Metrics]]
|-
|Subject || Suspected machine issue (* || Not an actionable email at this point. (from: nobody@cruncher - s/a {{bug|825625}}
|-
|Subject ||Talos Suspected machine issue *|| ''if you don't know, you don't care''
|-
|Subject ||Try submission *||to: autolanduser@mozilla.com
|-
|Subject ||[vcs2vcs] alert_major_errors* || '''major processing error''' make sure build duty and/or hwine know [[#vcs2vcs|details]]
|-
|Subject ||[vcs2vcs]: git.m.o push N failed: * || single occurrence related to git.m.o/releases/gecko.git '''if repeated, this is a major processing error''' make sure build duty and/or hwine know [[#vcs2vcs|details]]
|-
|Subject ||[vcs2vcs] process delays* || '''if repeated, this is a major processing error''' make sure build duty and/or hwine know [[#vcs2vcs|details]]
|-
|Subject || [release-runner] failed || [[#What_to_do_when_one_is_received_6| How to investigate release runner failures]]. ''(ignore if a release isn't actively being started)''
|-
|To || release+aws@mozilla.com || AWS admin email, service notifications & marketing. See [[#Amazon_EC2_Instance_scheduled_for_retirement|list of AWS emails]], contact catlee if unsure how to handle.
|-
|To || release+bitbucket@mozilla.com || Mozilla Bitbucket Admin email (contact hwine for now)
|-
|To || release+vcs2vcs@mozilla.com || Output from vcs2vcs hg<->git conversion ([[#vcs2vcs|details]])
|-
|To || release+aws-sanity-check@mozilla.com || Output from cruncher [http://hg.mozilla.org/build/cloud-tools/file/default/aws/aws_sanity_checker.py aws_sanity_checker.py] (contact rail)
|-
|To || release+ec2.*@mozilla.com || error output from crontab on the indicated machine. FIX ISSUE!
|-
|To || release+sns@mozilla.com || SNS issue notifications from various services. FIX ISSUE!
|-
|To || release+update.b2g.o@mozilla.com || low disk space on dogfood update server, see {{bug|877224}}
|-
|To || release+chromecast@mozilla.com || Developer account for Chromecast app support {{bug|1037018}} ([[#chromecast|details]])
|}

<br />

__TOC__

=Performance Metrics=
== Why we get them ==
We get various emails containing raw data that relates to a performance bottle neck at some point in time. Typically these are produced by cron jobs, and so received regularly regardless of metric status. (I.e. they may not require any action.)

== What is sending them ==
Since this is a "catch all" category, various tools send them. Check the full headers for information on sender and source machine as needed.

== What to do when one is received ==
If you don't know what it's about, you don't need to deal with it beyond setting up a filter to ignore it.

== How to silence or acknowledge this alert ==
It's not an alert, so they'll keep coming until the end of time. Filter them if you're not involved with them.

== Future plans ==
Adhoc, so varies by email. Theoretically, these ''should'' be transitional, and moved into automation and alerting as soon as the metric is understood.

== How to best filter these emails ==
Since these are adhoc, you'll need adhoc filters. It would be nice if folks used a common prefix on subjects, such as "<tt><nowiki>[releng metrics]</nowiki></tt>".

<div id="vcs2vcs"> </div>
= vcs2vcs System=
== Why we get them ==
These emails are the interim notification for vcs2vcs system, and indicate an error that must be addressed. The b2g project is dependent upon parts of the vcs2vcs system, as are other developers and partners.

== What is sending them ==
All emails are sent (perhaps indirectly) by a script from [http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/ vcs2vcs tools]. The hosts sending the email will be one of the ones listed in [http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/file/default/status the configs]. Full details of how each script is run, including trouble shooting tips, are in the [http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/file/default/docs docs] (a formatted copy ''may'' be online [http://people.mozilla.com/~hwine/tmp/vcs2vcs/ here]).

== What to do when one is received ==
* if the subject contains "[vcs2vcs] AUTOFIX process delays", then look for another email within a few minutes and proceed as follows:
** if a second email from the same host follows almost immediately with a subject of "[vcs2vcs] process delays", then the AUTOFIX failed, which is an unexpected condition. Page hwine.
** if no followup email is received, the AUTOFIX worked. Log in {{bug|829025}} & delete (or just delete and leave for hwine to log).
* if the subject contains "[vcs2vcs] process delays" '''''and''''' is repeated every 20 minutes, this is a service outage - one or more repositories are no longer being updated. The email contents will give specific errors. Consult the trouble shooting section of the docs (above) for guidance and/or PAGE hwine.
** Unfortunately, there appear to be a few race conditions between scripts, so a single occurrence of the email may be a false positive. ({{bug|839595}} filed to track this.)

* if the subject contains "[vcs2vcs] alert_major_errors alert", this is a major problem - one or more repositories are no longer being updated. The email contents will give specific errors. Consult the trouble shooting section of the docs (above) for guidance and/or contact hwine.
** The most common cause of this is hg repo corruption, the recovery is scripted, but can take some time. Please add to {{bug|808129}} if you fix, or block that bug with a new bug.
** NOTE: you may receive an additional email after the root cause is resolved. (The alert checks on the hour for problems in the prior hour.)

* if the subject containes "[vcs2vcs]: git.m.o push N failed for gecko.git:", this is a (usually) transient problem with pushing gecko.git (the partner facing gecko repository) to either git.m.o or git staging. Two pushes are tried each iteration - both should succeed. Each push is numbered '1' or '2', if you see only one email report, the other already succeeded, and is ignorable. One or two sets of emails is ignorable, any more needs investigation, starting with the health of git.mozilla.org. (Note that the message is short, as this also pages hwine via sms, where brevity is nice.)

* if the subject is something else, this is likely unexpected output from a cron job. Judge the severity and escalate to hwine appropriately. File a bug to get better diagnosis of this error condition in the future.

== How to silence or acknowledge this alert ==
Resolving the root cause will stop the emails.

== Future plans ==
The system will eventually be transitioned to IT for operations. Specific email will be converted to nagios alerts before then.

== How to best filter these emails ==
All of these emails are sent to the addresses of the form: <tt>release+vcs2vcs*@mozilla.com</tt>. Common sub addresses are:
; release+vcs2vcs : mail that will have specifics in the Subject line.
; release+vcs2vcs+forward : mail to vcs2vcs user, forwarded via <tt>~/.forward</tt> file.

= Release runner =
== Why we get them ==
Release runner sends e-mail when it fails in any way. Eg, failing to poll ship it after a long period of time or failing to start a submitted release.

== What is sending them ==
* Source: https://hg.mozilla.org/build/tools/file/default/buildfarm/release
* Sent by: buildbot
* Runs on: buildbot-master36 through supervisord

== What to do when one is received ==
[[Release:Release_Automation_on_Mercurial:Troubleshooting#How_to_investigate_release_runner_failures | How to invesigate release runner failures]]

== How to silence or acknowledge this alert ==
Fix whatever problem release runner has hit. (Sometimes this means waiting out network issues.) There's no way to ack (in the nagios sense) release runner e-mails.

== Future plans ==
They're here to stay.

== How to best filter these emails ==
[release-runner] in the subject.

=Amazon EC2 Instance scheduled for retirement=
==Example==
One or more of your Amazon EC2 instances in the us-east-1 region is scheduled for retirement. The following instance(s) will be shut down after 12:00 AM UTC on 2013-10-22.

i-02cc2669

== Why we get them ==
Amazon needs us to move our virtual instance(s) off of certain physical hardware so they can perform maintenance on it.

== What is sending them ==
Automated notification sent by no-reply-aws@amazon.com

== What to do when one is received ==
* determine what host is running on the specified EC2 instance.
* power the instance down in an orderly manner
* start it back up

== How to silence or acknowledge this alert ==

== Future plans ==

== How to best filter these emails ==
Filter on the sender and subject line.

<div id="chromecast"></div>
= Mail to release+chromecast@mozilla.com =
== Why we get them ==
The mobile team is adding Chromecast support (ability to fling videos/tabs from a device to a TV). They need a persistent account not linked to a single developer who might leave the company at some point.

== What is sending them ==
These emails come from the

== What to do when one is received ==
Traffic should be light. If the email is not simply Google self-promotion, please forward it to lead mobile devs, namely :blassey and :mfinkle.

== How to silence or acknowledge this alert ==

== Future plans ==

== How to best filter these emails ==
You can either filter on the "To:" field for "release+chromecast@mozilla.com" to catch just these emails, or filter on "From:" for "noreply@google.com" and move all mail from Google (we have multiple accounts mailing us intermittently) to a separate Google subfolder (coop).

<hr />
<small>

=Sample=
== Why we get them ==
Give a brief explanation of why this email is for, what it helps us do and why it should be watched

== What is sending them ==
Include a link to the source of the program sending the email. Include information on which hosts are sending the email, and give information on how program runs. Is it a daemon? Does it have an init script? Do you run it under screen?

== What to do when one is received ==
* if the title contains "[scl-production-puppet-new] <slavename> is waiting to be signed", this is for information and requires no immediate action
* if the title contains "[scl-production-puppet-new] <slavename> has invalid cert", the script will try once to clean the cert before sending the email. If this is successful, you'll see a matching "<slavename> is waiting to be signed" email. The key will be automatically signed

== How to silence or acknowledge this alert ==
Include information on how to make the emails stop

== Future plans ==
provide any future plans for this email. Is it temporary? Is it going to be replaced by a real dashboard? Are you going to add/change things people filter on?

== How to best filter these emails ==
provide insight on how to filter these emails. Is there a distinguishing header? Is it always from a specifc host, or family of hosts? Is there a distinctive subject?
</small>

ReleaseEngineering/PuppetAgain/Modules/log aggregator

2015-03-04T14:37:19Z

Arich: log aggregation module docs

This module configures log aggregation servers to collect logs via rsyslogd and clients to send logs to the log aggregation server CNAME/LoadBlanacer in their datacenter or region. It installs rsyslog on the aggregation servers and modifies the syslog configuration of clients based on operating system type.

Log aggregation servers should include toplevel::server::log_aggregator

All POSIX hosts are clients and receive the client configuration as part of modules/toplevel/manifests/base.pp: include log_aggregator::client

The correct aggregation host is chosen based on the FQDN of the client in manifests/moco-config.pp:

<pre>
$log_aggregator = $fqdn ? {
/.*\.scl3\.mozilla\.com/ => 'log-aggregator.srv.releng.scl3.mozilla.com',
/.*\.use1\.mozilla\.com/ => 'log-aggregator.srv.releng.use1.mozilla.com',
/.*\.usw2\.mozilla\.com/ => 'log-aggregator.srv.releng.usw2.mozilla.com',
default => '',
}
</pre>

In AWS, the golden AMIs we use in all regions are always generated in use1, so we use rsyslog stanzas in cloud-init to overwrite the client rsyslog file to specify the correct log aggregation host per https://github.com/mozilla/build-cloud-tools/pull/45

ReleaseEngineering/PuppetAgain

2015-02-19T19:58:41Z

Arich: /* added new modules */

<div style="float: right; border: thin black solid; padding: 2em;">
A sysadmin asked the Architect,
:"What's the best way to install a new system?"
The Architect answered,
:"Turn it on."
The sysadmin was enlightened.
</div>

= Documentation - Manifests & Modules =

The Puppet manifests themselves are documented here. Any new modules should be added to the proper list below.

== Modules ==

All substantial configuration is done with puppet modules, in the <tt>modules</tt> directory. Each should have its own page describing both how to use the module, and how the module works, below:

=== Infrastructure ===

These modules are part of the puppet system itself, and provide support to other modules as needed

* [[ReleaseEngineering/PuppetAgain/Modules/config]] - global configuration
* [[ReleaseEngineering/PuppetAgain/Modules/dirs]] - Common directories
* [[ReleaseEngineering/PuppetAgain/Modules/packages]] - install packages generically
* [[ReleaseEngineering/PuppetAgain/Modules/puppet]] - install, upgrade, and run puppet (including custom facts, etc.)
* [[ReleaseEngineering/PuppetAgain/Modules/toplevel]] - top-level classes for node types, included from node definitions
* [[ReleaseEngineering/PuppetAgain/Modules/shared]] - shared calculated values, functions, facts, etc.
* [[ReleaseEngineering/PuppetAgain/Modules/users]] - user account management
* [[ReleaseEngineering/PuppetAgain/Modules/puppetmaster]] - install, upgrade and run puppet master

=== Action ===

These modules actually get stuff done.

* [[ReleaseEngineering/PuppetAgain/Modules/androidemulator]] - install and configure Android emulators
* [[ReleaseEngineering/PuppetAgain/Modules/auditd]] - install and configure auditd
* [[ReleaseEngineering/PuppetAgain/Modules/aws]] - manage instance storage
* [[ReleaseEngineering/PuppetAgain/Modules/aws_manager]] - install and manage AWS related management scripts
* [[ReleaseEngineering/PuppetAgain/Modules/b2g_bumper]] - install and configure the b2g_bumper service
* [[ReleaseEngineering/PuppetAgain/Modules/bmm]] - configure all the components of a Mozpool imaging server
* [[ReleaseEngineering/PuppetAgain/Modules/bors]] - bors installation
* [[ReleaseEngineering/PuppetAgain/Modules/bouncer_check]] - create a python virtualenv and install and configure the check_bouncer nagios check
* [[ReleaseEngineering/PuppetAgain/Modules/buildslave]] - buildslave (buildbot) installation and startup
* [[ReleaseEngineering/PuppetAgain/Modules/buildmaster]] - buildmaster (buildbot) installation and startup
* [[ReleaseEngineering/PuppetAgain/Modules/casper]] - create the casper user for OS X
* [[ReleaseEngineering/PuppetAgain/Modules/ccache]] - ccache directory management
* [[ReleaseEngineering/PuppetAgain/Modules/clean]] - cleanup tasks
* [[ReleaseEngineering/PuppetAgain/Modules/cleanslate]] - install cleanslate into a python virtualenv
* [[ReleaseEngineering/PuppetAgain/Modules/collectd]] - configure collectd
* [[ReleaseEngineering/PuppetAgain/Modules/cron]] - install and start the cron daemon
* [[ReleaseEngineering/PuppetAgain/Modules/diamond]] - install and configure diamond metrics collection software
* [[ReleaseEngineering/PuppetAgain/Modules/disableservices]] - disable unneeded services
* [[ReleaseEngineering/PuppetAgain/Modules/dnsmasq]] - install and start dnsmasq
* [[ReleaseEngineering/PuppetAgain/Modules/foopy]] - build foopies
* [[ReleaseEngineering/PuppetAgain/Modules/fw]] - simple interface for host firewall configuration
* [[ReleaseEngineering/PuppetAgain/Modules/gaia_bumper]] - bump gaia (nicely, of course)
* [[ReleaseEngineering/PuppetAgain/Modules/ganglia]] - configure ganglia
* [[ReleaseEngineering/PuppetAgain/Modules/git]] - exec to clone specified git repos
* [[ReleaseEngineering/PuppetAgain/Modules/grub]] - configure grub for linux hosts
* [[ReleaseEngineering/PuppetAgain/Modules/gui]] - configure a GUI environment
* [[ReleaseEngineering/PuppetAgain/Modules/hardware]] - hardware-specific stuff
* [[ReleaseEngineering/PuppetAgain/Modules/httpd]] - install and configure httpd server
* [[ReleaseEngineering/PuppetAgain/Modules/instance_metadata]] - obtain instance metadata on AWS hosts and dump it into a file
* [[ReleaseEngineering/PuppetAgain/Modules/jacuzzi_metadata]] - obtain jacuzzi metadata on AWS hosts and dump it into a file
* [[ReleaseEngineering/PuppetAgain/Modules/log_aggregator]] - configured centralized logging
* [[ReleaseEngineering/PuppetAgain/Modules/mercurial]] - manage hg repositories
* [[ReleaseEngineering/PuppetAgain/Modules/mig]] - install and configure mig_agent
* [[ReleaseEngineering/PuppetAgain/Modules/mockbuild]] - manage mock build environments
* [[ReleaseEngineering/PuppetAgain/Modules/mozpool]] - configure all the components of a Mozpool server
* [[ReleaseEngineering/PuppetAgain/Modules/needs_reboot]] - handle reasons that a system might need to be rebooted
* [[ReleaseEngineering/PuppetAgain/Modules/network]] - configure host networking parameters
* [[ReleaseEngineering/PuppetAgain/Modules/nginx]] - install nginx
* [[ReleaseEngineering/PuppetAgain/Modules/nrpe]] - NRPE support
* [[ReleaseEngineering/PuppetAgain/Modules/ntp]] - NTP support
* [[ReleaseEngineering/PuppetAgain/Modules/pkgbuilder]] - set up a host to build OS packages
* [[ReleaseEngineering/PuppetAgain/Modules/powermanagement]] - configure power management
* [[ReleaseEngineering/PuppetAgain/Modules/powershell]] -
* [[ReleaseEngineering/PuppetAgain/Modules/proxxy]] - install and configure nginx to act as a reverse proxy
* [[ReleaseEngineering/PuppetAgain/Modules/rdp]] - enable windows RDP
* [[ReleaseEngineering/PuppetAgain/Modules/releaserunner]] - install release runner
* [[ReleaseEngineering/PuppetAgain/Modules/rsyslog]] - rsyslog configuration
* [[ReleaseEngineering/PuppetAgain/Modules/runner]] - install runner and manage pre-flight tasks
* [[ReleaseEngineering/PuppetAgain/Modules/screenresolution]] - set GUI screen resolution
* [[ReleaseEngineering/PuppetAgain/Modules/selfserve_agent]] - install the BuildAPI self-serve agent
* [[ReleaseEngineering/PuppetAgain/Modules/shipit_notifier]] - install and configure shipit_notifier in a python virtualenv
* [[ReleaseEngineering/PuppetAgain/Modules/signingserver]] - configure a signing server instance
* [[ReleaseEngineering/PuppetAgain/Modules/slaveapi]] - configure a slaveapi server instance
* [[ReleaseEngineering/PuppetAgain/Modules/slaverebooter]] - install and configure slaverebooter
* [[ReleaseEngineering/PuppetAgain/Modules/slave_secrets]] - add secrets to slaves
* [[ReleaseEngineering/PuppetAgain/Modules/smarthost]] - configure a mail relay
* [[ReleaseEngineering/PuppetAgain/Modules/ssh]] - manage ssh configuration (server, global, and user)
* [[ReleaseEngineering/PuppetAgain/Modules/talos]] - talos slave specific settings
* [[ReleaseEngineering/PuppetAgain/Modules/tftpd]] - tftpd (and xinetd) configuration
* [[ReleaseEngineering/PuppetAgain/Modules/timezone]] - set the system timezone
* [[ReleaseEngineering/PuppetAgain/Modules/tweaks]] - small, one-off classes (aka "miscellaneous")
* [[ReleaseEngineering/PuppetAgain/Modules/vnc]] - configure the VNC server
* [[ReleaseEngineering/PuppetAgain/Modules/web_proxy]] - configure the system to use a proxy to access the web

=== Utility ===

These modules are more generic, and probably useful outside of PuppetAgain.
* [[ReleaseEngineering/PuppetAgain/Modules/kernelmodule]] - install a Linux kernel module
* [[ReleaseEngineering/PuppetAgain/Modules/motd]] - edit the contents of /etc/motd
* [[ReleaseEngineering/PuppetAgain/Modules/osxutils]] - utility for reading and writing configuration using defaults and system setup on MacOSx
* [[ReleaseEngineering/PuppetAgain/Modules/python]] - support for installing python virtualenvs and packages
* [[ReleaseEngineering/PuppetAgain/Modules/shellprofile]] - add items to users' default shell profile
* [[ReleaseEngineering/PuppetAgain/Modules/sudoers]] - manage sudo permissions
* [[ReleaseEngineering/PuppetAgain/Modules/supervisord]] - supervise processes

=== Third-Party ===

These are modules taken from elsewhere. When adding, remember to verify license compatibility and ensure proper credit.

* assert - from https://github.com/binford2k/puppet-assert
* sysctl - from https://github.com/duritong/puppet-sysctl
* concat - from https://github.com/ripienaar/puppet-concat (modified to not use a fact, although this should probably be reverted)
* firewall - from https://github.com/puppetlabs/puppetlabs-firewall/
* stdlib - from https://github.com/puppetlabs/puppetlabs-stdlib/
* vmwaretools - from https://github.com/craigwatson/puppet-vmwaretools
* Windows Firewall - from https://forge.puppetlabs.com/liamjbennett/windows_firewall
* Windows Registry - from https://forge.puppetlabs.com/puppetlabs/registry

== Bugs ==

Bugs for work on PuppetAgain should be filed in the [https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=nobody%40mozilla.org&attach_text=&blocked=&bug_file_loc=http%3A%2F%2F&bug_severity=normal&bug_status=NEW&comment=&component=RelOps%3A%20Puppet&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&defined_groups=1&dependson=&description=&flag_type-354=X&flag_type-4=X&flag_type-407=X&flag_type-481=X&flag_type-607=X&flag_type-674=X&flag_type-707=X&flag_type-791=X&flag_type-800=X&flag_type-811=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=All&priority=--&product=Infrastructure%20%26%20Operations&qa_contact=dustin%40mozilla.com&rep_platform=All&requestee_type-4=&requestee_type-607=&requestee_type-791=&requestee_type-800=&short_desc=&status_whiteboard=&target_milestone=---&version=other Infrastructure & Operations - Relops: Puppet] Component.

= How To =

* [[ReleaseEngineering/PuppetAgain/HowTo/Re-issue Certificates for a host]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Set up a user environment]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Add new secrets]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Bootstrap a Puppetmaster]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Remove a Puppetmaster]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Change secrets]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Build RPMs]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Build DMGs]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Build DEBs]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Hack on PuppetAgain]] (patch/review guidelines)
* [[ReleaseEngineering/PuppetAgain/HowTo/Anchor Classes]] (getting dependencies right)
* [[ReleaseEngineering/PuppetAgain/HowTo/Add Files to Data]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Merge Changes Between Repos]]
* [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Read_Releng-Shared_Emails How To read releng-shared Emails] (moco releng-only)

= System Description =

This section describes how PuppetAgain is built at Mozilla. External implementations may not have all of these bells and whistles. [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=22381625 This link] contains details oriented toward Mozilla IT and ops folks.

== The Goals ==

* PuppetAgain should be usable as a whole for folks outside of Mozilla, Inc. who want to build similar systems (see "Organizations" below)
* Client images should proceed automatically from base image install to a fully-operational state. While refimages may be employed, this is done only as an optimization.
* We do not keep distinct reference images. Reference images are used only as an optimization to avoid pounding the puppet servers when installing dozens of new hosts. When a new refimage snapshot needs to be made, a fresh machine is rebuilt from scratch, snapshotted, and then returned to service.
* OS does not imply role. Roles are defined in node declarations, by including <tt>toplevel::*</tt> classes.
* Include all necessary dependencies. Debugging dependency errors when building a new reference system is no fun.
* Documentation (here) is a part of the patch.
See [[ReleaseEngineering/PuppetAgain/HowTo/Hack on PuppetAgain]] for more detail

== Organizations ==

Each distinct instance of puppetagain is referred to as an organization, and tagged with a short identifier (e.g., "moco" for the mozilla releng instance, or "seamonkey" for seamonkey). Within an organization, configuration and secrets are shared, and everything runs from the same set of manifests. Configuration and secrets can differ between organizations.

== Puppetmasters ==

PuppetAgain masters are managed by PuppetAgain. Each organization can have 1 or more masters, arranged in a cluster (with one cluster per organization). There is one "distinguished master" in the cluster. This master is distinguished only for purposes of simplifying synchronization -- the cluster will continue to operate indefinitely without the distinguished master, although master-master communication (secrets and CRLs) will not work.

See the following for more details, noting that most of this is not required for an external PuppetAgain implementation.
* [[ReleaseEngineering/PuppetAgain/Puppetmasters]]
* [[ReleaseEngineering/PuppetAgain/Puppetization Process]]
* [[ReleaseEngineering/PuppetAgain/Certificate Chaining]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Bootstrap a Puppetmaster]]

== Puppet Versions ==

The releng puppet infrastructure will strive to keep up to date with the most recent stable versions released by Puppet Labs.

== Base Images and Puppetizing ==

The base images for this infrastructure are barely-modified OS installs. They have just enough installed that they can connect to a puppet server, get certificates, and puppetize on boot.

* [[ReleaseEngineering/PuppetAgain/Base Images]]
* [[ReleaseEngineering/PuppetAgain/Puppetization Process]]

Note that, while most of PuppetAgain is intended to be easily replicated, the deployment system is probably not easily replicated, and is best left out of any external implementations.

== Custom Facts, Functions, Types, and Providers ==

Custom code is documented in the page for the module that contains it. Code that doesn't have a more appropriate home is in [[ReleaseEngineering/PuppetAgain/Modules/shared|shared]].

== Stages ==
Stages need to be defined globally in Puppet manifests, and this is done in <tt>manifests/stages.pp</tt>. The following stages are available, aside from 'main', the default stage.

* network - This stage should handle any network related configurations for some specific cases (like AWS)
* packagesetup - This stage should handle any preliminaries required for package installations, so that subsequent package installations do not need to require them explicitly.
* users - This stage creates user accounts; while this is normally automatically required, the requirement doesn't work with the temporary 'darwinuser' type.

== Nodes ==

<tt>manifests/nodes.pp</tt> defines all of the nodes the puppet masters recognize. Note that all nodes are defined for all masters. This file is a symlink to <tt>$org-nodes.pp</tt>, e.g., <tt>moco-nodes.pp</tt>. With this arrangement, each organization can make node changes without any risk to other organizations.

In anticipation of using an external node classifier (ENC), node definitions should only include classes - do not define any resources within nodes. In general, the included classes should be in the [[ReleaseEngineering/Puppet/Modules/toplevel|toplevel]] module.

Host-specific values are specified as node-scope variables, as these are easier to represent in an ENC. Such variables (including some Puppet gotchas) are described in [[ReleaseEngineering/PuppetAgain/node-scope variables|node-scope variables]].

Node definitions also specify a host's [[ReleaseEngineering/PuppetAgain/Aspects|aspects]], e.g., <tt>$aspects = [ 'staging' ]</tt>.

== Configuration ==

Per-organization configuration is read from <tt>manifests/config.pp</tt>, which is a symlink to <tt>$org-config.pp</tt>, similar to that for nodes. The <tt>config.pp</tt> file defines a "config" class that inherits from "config::base". It is free to express the configuration using any mechanism available to puppet. For some organizations, simple puppet literals will do, while more complex organizations will want to perform some more sophisticated automatic generation of configuration. See [[ReleaseEngineering/PuppetAgain/Modules/config|config]] for more.

== Secrets and External Data ==
See [[ReleaseEngineering/PuppetAgain/Secrets]] and [[ReleaseEngineering/PuppetAgain/Extsync]].

== Data ==

Puppet deals with a lot of big files - packages, mostly. We don't want these in hg! They are instead managed as data. This means several big file trees available at http://repos/$treename and, from puppet, at puppet://$treename. See [[ReleaseEngineering/PuppetAgain/Data]] for details on what's available, how it is implemented, and some how-tos.

This data is available outside of Mozilla via HTTP and rsync at http://puppetagain.pub.build.mozilla.org/data and rsync://puppetagain.pub.build.mozilla.org/data.

== Packages ==

See [[ReleaseEngineering/PuppetAgain/Packages]] for information about proper handling of packages in PuppetAgain.

== Aspects ==

Taking a page from [http://en.wikipedia.org/wiki/Aspect-oriented_programming Aspect Oriented Programming], PuppetAgain implements Aspect Oriented Puppet. Aspects cross-cut the concerns represented by the toplevel hierarchy. For example, whether a host is a staging host, whether it is loaned out, etc. See [[ReleaseEngineering/PuppetAgain/Aspects]] for details.

== Source Code ==

The manifests are at http://hg.mozilla.org/build/puppet.

= History =

Releng once used [[ReleaseEngineering/Puppet|a puppet infrastructure]] based on Puppet-0.24.8, and manifests at http://hg.mozilla.org/build/puppet-manifests/. This had a few weaknesses:
* lots of assumptions and fragile dependencies based on bugs in 0.24.8
* very few modules - mostly manifest files, organized per slave type, rather than per service/purpose
* many references to external files which are not as available as the repo itself
* puppet manifests assume some manual ref-image steps; external exact reproduction is extremely difficult

Dustin started work on a new puppet deployment - chronicled at [[User:Djmitche/New Releng Puppet Infrastructure]]. That's this puppet.

Platform/2014-Q3-Goals

2014-09-30T16:35:50Z

Arich:

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
Items marked [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 here] with release 33 and 34 are part of the Q3 landings.

=== Layout ===
* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Enable Vertical Text for major use cases for Chinese & Japanese
** {{miss|{{bug|145503}}}} - Meta Bug. We've made lots of progress, but our big bug won't get closed until Q4
** {{done|{{bug|789096}}}} - Layout with horizontal block flow and vertical text flow
** {{ok|{{bug|902762}}}} - Vertical text run creation
** {{risk|{{bug|1062963}}}} - Make nsFloatManager use logical coordinates

* Text Performance
** We'll get 1 of the 3 we wanted to hit.
** {{ok|{{bug|998869}}}} Streamline parsing of fontlists and improve efficiency of font matching code (note: unicode-range support will fall out of this work)
** {{miss|{{bug|934770}}}} - slow at rendering large blocks of plain text
** {{miss|{{bug|860492}}}} - Divide large text runs into smaller runs to avoid chrome hangs

* Improve Restyling Performance
** {{done|{{bug|977991}}}}
** {{done|{{bug|931668}}}} - (not originally listed for this quarter, but carryover from previous)

* {{drop|Font Inflation and Reflow-on-Zoom }}
** We picked up scrolling features/fixes in Q3 and deferred this item
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* ImageLib
** {{ok|RasterImage for multiple images}}
*** {{done|prerequisite draw API refactoring}} {{bug|1043560}}
*** {{done|store imgFrame objects in the imagelib SurfaceCache}} {{bug|1054079}}
*** {{done|use #1: HQ scaled frames in the surface cache}} {{bug|1060200}}
*** {{ok|use #2: store multiple decode options in surface cache for non-animated images}}
*** {{risk|use #3: store multiple decode options in surface cache for animated images}}

* CSS Projects with Adobe
** {{done|CSS Filters}}

* Animations & Transitions
** {{risk|transitions/animations spec editing}}
** {{risk|transitions refactoring to match new spec}}
*** {{done|{{bug|996796}}}} landed, but work is ongoing for {{bug|960465}}
** {{done|frame reconstruction (625289)}}
** {{risk|Effective start of CSS animations and transitions {{bug|927349}}}}
*** may spill into Q4

* OMTA on non-B2G Platforms (980770)
** {{risk|fix correctness bugs (cascading, etc.)}}
*** partly done in {{bug|996796}}, but cascading fix likely miss
** {{risk|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{done|Get basic implementation of GetAnimationPlayers {{bug|1032573}}}}
** {{risk|Implement PlaybackControl() {{bug|1033114}}}}
*** may spill into Q4

* CSS Scrolling
** {{ok|CSS scroll snapping}}
** {{ok|scroll-behavior:smooth}}

* CSS Flexbox
** {{ok|performance bugs}}
*** significant improvement on {{bug|946167}}, though more to do
** {{ok|spec changes}}
*** completed {{bug|984711}}/{{bug|1037177}}/{{bug|1015474}} on min-width/height: auto
*** completed {{bug|1032922}} and followups on flex-basis: main-size rename
*** abs-pos handling at-risk (picked up object-fit/position instead)

* CSS Ruby
** Our intern got through a bunch of this, but we'll continue it next quarter; remaining work tracked in {{bug|css-ruby}} and {{bug|enable-css-ruby}}
** {{done|style system support}}
** {{done|frame construction}}
** {{done|anonymous box handling}}
** {{done|reflow architecture and horizontal positioning}}
** {{miss|line breaking}}
** {{miss|vertical positioning}}
** {{miss|other dependencies on enabling the feature}}

=== Media ===
* {{miss|Enable YouTube MSE/VP9 for Firefox 33 in Nightly/Aurora {{bug|1000686}}}}
* {{miss|Enable YouTube MSE/MP4 on Windows and Firefox OS for Firefox 34}}

'''Detailed Breakdown'''
* MSE Common
** {{done|Rate adaption/buffer switching, reseting}}
** {{miss|Seeking into unbuffered ranges {{bug|1056440}}}}
** {{todo|Eviction/pinning}}
* MSE WebM
** {{done|WebM segment parser {{bug|881512}}{{bug|1044498}}}}
* MSE MP4
** {{done|MP4 segment parser {{bug|1027875}}{{bug|1057203}}}}
** MP4 Demuxer
*** {{done|Integrate stagefright MP4 demuxer {{bug|908503}}}}
*** {{done|Accurate range reporting {{bug|1045909}}}}
*** {{done|CENC support {{bug|1022434}}}}
*** {{todo|DASHIF and other players aside from YouTube {{bug|1039149}}}}
** H.264/AAC Decoder
*** {{done|MP4/fMP4 platform decoder module for Mac OSX {{bug|941296}}}}
*** {{miss|MP4 support on Firefox OS {{bug|1060900}}}}
**** {{done|MP4 platform decoder module for Firefox OS {{bug|941302}}}}
**** {{miss|Use a single shared decoder for MSE on b2g {{bug|1036849}}}}

=== DOM ===
* {{done|Mirror prototype of DOM objects through xray wrappers ({{bug|787070}}, peterv)}}
* {{drop|Remove nsDOMClassInfo.cpp}}
** Given the recent focus on e10s, we have not been pushing on this at this point.
* {{done|Make less-privileged non-Xrayable unwaived opaque from privileged code (bholley, {{bug|856067}})}}
* {{done|Route all JSContext pushing through AutoJSAPI and Implement GetEntryGlobal (bobowen, bholley, {{bug|951991}})}}
* {{miss|Land <picture> preffed on on nightly ({{bug|1017875}}) (johns)}}
** John got pulled into e10s plugin work ({{bug|874016}}) but made excellent progress here and was ''very'' close to preffing on by the end of Q3.
* {{done|audit callsites of IsInDoc()/GetCurrentDoc to ensure correct Shadow DOM behaviour and fix Shadow DOM blockers for Gaia (smaug, wchen) ({{bug|1026047}})}}
* {{miss|land Service Workers preffed off on nightly (nsm, bkelly, baku) ({{bug|903441}})}}
** This is progressing well, but won't be *done* until the end of the quarter, so still on track.
** Note that originally we thought things would be at the point where Gecko and Blink would be far enough along with a stable spec that this could be preffed on. That is not going to be the case but we are still aiming to have a usable implementation preffed off.
** There remain spec questions about Cache which have impacted the design of our implementation.
** We are focusing on [https://tbpl.mozilla.org/?tree=Maple Maple] being usable for getting feedback.

=== WebAPI ===
* {{done|create design plan for "share" activity (flow, what kind of objects are involved) (annevk)}}
** https://wiki.whatwg.org/wiki/Sharing
* {{miss|document existing activities usage in gaia (ehsan)}}
** this work is underway but it's not yet complete
* {{ok|get [https://w3c.github.io/screen-orientation/ screen orientation spec] to LC (marcosc)}}
* {{done|publish [http://www.w3.org/TR/wake-lock-use-cases/ use cases for wake locks] (marcosc)}}
* {{ok|publish spec for [http://w3c.github.io/wake-lock/ "wakelock" API] (marcosc)}}
* {{done|24/12 hour format API (ehsan) {{bug|903683}}}}
* {{miss|{{bug|942542}} new quota API on PBackground for Service Worker cache (janv)}}
** this is up for review but won't land before the end of Q3
* {{miss|{{bug|701634}} IndexedDB in workers (bent)}}
** the majority of this work was done with {{bug|994190}} to get main thread IDB using PBackground but the remaining work to get IndexedDB available on workers did not make it

=== JS ===
* {{miss|ES6 classes: }}{{Bug|837314}}
* {{jok|1020751}} Generational GC on Firefox OS
* {{jok|650161}} Compacting GC to reduce memory usage
* {{jok|856533}} Escape analysis JIT optimizations
* {{done|Use Latin1 strings to reduce memory usage: }}{{Bug|998392}}
* {{jok|903519}} Allocate strings in GC nursery (for performance)
* {{miss|ARM64 JIT ''[stretch goal]'': }} {{Bug|972710}}

=== Accessibility ===
* {{miss|}}e10s: proxy the common a11y API stuff like name, role, and states.
** Decent progress with unlanded patches including some event work.
* {{done|}}GAIA: Fix [https://bugzilla.mozilla.org/buglist.cgi?priority=--&f1=blocked&list_id=10674217&o1=anyexact&resolution=---&query_based_on=b2ga11y%20p%3D1&o2=substring&query_format=advanced&f2=status_whiteboard&v1=893789&component=Disability%20Access%20APIs&component=Gaia&component=Gaia%3A%3ABluetooth%20File%20Transfer&component=Gaia%3A%3ABrowser&component=Gaia%3A%3ABuild&component=Gaia%3A%3ACalendar&component=Gaia%3A%3ACamera&component=Gaia%3A%3AClock&component=Gaia%3A%3AContacts&component=Gaia%3A%3ACost%20Control&component=Gaia%3A%3ADialer&component=Gaia%3A%3AE-Mail&component=Gaia%3A%3AEverything.me&component=Gaia%3A%3AFirst%20Time%20Experience&component=Gaia%3A%3AFMRadio&component=Gaia%3A%3AGallery&component=Gaia%3A%3AGithubBot&component=Gaia%3A%3AHomescreen&component=Gaia%3A%3AKeyboard&component=Gaia%3A%3AL10n&component=Gaia%3A%3ALoop&component=Gaia%3A%3AMusic&component=Gaia%3A%3ANotes&component=Gaia%3A%3APDF%20Viewer&component=Gaia%3A%3APerformanceTest&component=Gaia%3A%3ARingtones&component=Gaia%3A%3ASearch&component=Gaia%3A%3ASettings&component=Gaia%3A%3ASMS&component=Gaia%3A%3ASystem&component=Gaia%3A%3ASystem%3A%3ABrowser%20Chrome&component=Gaia%3A%3ASystem%3A%3AInput%20Mgmt&component=Gaia%3A%3ASystem%3A%3ALockscreen&component=Gaia%3A%3ASystem%3A%3AWindow%20Mgmt&component=Gaia%3A%3ATestAgent&component=Gaia%3A%3AUI%20Tests&component=Gaia%3A%3AVideo&component=Gaia%3A%3AWallpaper&component=Gaia%3A%3AWappush&v2=b2ga11y%20p%3D1&product=Core&product=Firefox%20OS all Gaia P1 a11y bugs] (~30 at this time).
** 49 (all) are fixed.
* {{done|}}FFOS: {{Bug|1030465}} - Volume change should update the screen reader volume.
* {{done|}}FFOS: {{Bug|1030466}} - Headphones screen reader volume is too low.
* {{done|}}FFOS: {{Bug|1030468}} - VC rectangle needs to work with scaled content.
* {{done|}}FFOS: {{Bug|1030470}} - Localization needs to work when switching locales in FxOS.

=== Perf ===

Fix major source of browser jank:

* {{ok|Initialize plugin instances asynchronously {{bug|998863}} }}
* {{ok|Pause heavy main-thread activities while user is interacting with the browser: }}
** {{ok|Determine when a user is actively interacting with the browser}}
** {{ok|Detect when jank occurs during interactions and report to Telemetry {{bug|1017055}} }}
** {{ok|Experiment with hinting to GC & CC that they should pause while the user is interacting with the browser}}
* {{ok|Help Frontend team with Places refactoring, eliminate some of the [http://telemetry.mozilla.org/slowsql/ Places main-thread SQL] reported to Telemetry }}
* {{ok|Don't store UI customization in localstore.rdf, use off-main thread JSON instead {{bug|559505}} }}

Improve Firefox startup (identified as a top issue in user research):

* {{ok|Reduce appearance of the "profile is in use" message on startup {{bug|286355}} }}
* {{ok|Restore windows one by one during session-restore {{bug|1034534}} and/or load windows by descending z-order {{bug|1034036}} }}
* {{ok|C++ version of AsyncShutdown {{bug|918317}} }}

Prevent performance regressions:

* {{ok|Implement automatic detection & alerting for Telemetry regressions {{bug|1031032}} }}
* {{ok|Help developers understand & diagnose Talos regressions}}, e.g. [https://bugzilla.mozilla.org/show_bug.cgi?id=1026550 Firefox 33 regression tracking], [https://bugzilla.mozilla.org/show_bug.cgi?id=1004427 Firefox 32 regressions], [https://bugzilla.mozilla.org/show_bug.cgi?id=990085 Firefox 31]

Grow community:

* {{ok|Mentor at least 5 external contributors}}

=== Networking ===

* {{miss|Ship Network Predictor ("Seer") on nightly, using HTTP cache instead of SQLite ({{bug|1009122}}) (hurley)}}
** Well-underway, but not done yet. Rolling over to Q4.
* {{done|Ship current (hopefully final) IETF version of HTTP/2 preffed on in nightly (hurley)}}
** HTTP/2 is done and we've shipped it. This is a big deal.
* {{done|HTTP/2 "alt-svc" support ({{bug|1003448}}) (mcmanus)}}
* {{drop|HTTP cache: determine if revalidation is needed w/o doing I/O ({{bug|983122}}) (sworkman) }}
** We didn't have the cycles to even start on this: decided it wasn't mission-critical.
* {{done|Network up/down link detection on all platforms ({{bug|939318}}) (bagder) }}
* {{drop|Implement WebSocket compression extension ({{bug|792831}}) (michal) }}
** Too much cache work remained for Michal to start on this. Also not mission-critical.

=== Mobile ===

=== A*Team ===

For full list, see [[Auto-tools/Goals/2014Q3|A-Team Goals 2014Q3]]

'''B2G'''
* {{drop|}} (moved to B2G team) Run a set of performance and correctness tests per-commit to b2g-inbound on Flame devices
* {{drop|}} (moved to B2G team) Get gaia-integration tests running on device
* {{done|}} Expand the FxOS Certification Suite with 1.4 support, test automation to prevent regressions, and investigation of support for non-phone devices
* {{done|}} Green up B2G tests on TaskCluster (joint with RelEng)

'''Developer Productivity'''
* {{ok|}} Deploy ReviewBoard for developers to start using (joint with RelEng)

'''Performance'''
* {{done|}} Deploy new Talos tests for tp5o_scroll, webgl, webrtc, and mainthread I/O
* {{ok|}} Get Datazilla alerts to beta mode (full parity with graph server alerts) with reduced noise
* {{done|}} Get Eideticker running against Android again with increased frequency
* {{done|}} Run B2G Eideticker against same branch/build combinations as our other on-device perf tests
* {{done|}} Stand up a Games Benchmarking system for webaudio tests running against Firefox and Chrome

'''Treeherder'''
* {{done|}} Deliver performance web service for ingesting and returning performance data
* {{miss|}} Deliver a UI for viewing Talos data

'''Sheriffing'''
* {{done|}} Fully transition sheriffing from TBPL to Treeherder

'''General Automation'''
* {{ok|}} Create weekly reports that describe how many tests have been added/disabled/enabled per suite and platform
* {{ok|}} Move reftest to mozbase
* {{done|}} Add command executors for Marionette for Java and Python

'''Bugzilla'''
* {{done|}} Improve load time of related bugs; can decrease show_bug load times by up to 12%
* {{ok|}} Minify and concatenate JS files
* {{ok|}} Authoritative view for review history
* {{ok|}} Rewrite docs for REST API

'''Community'''
* {{done|}} Create good_next_bugs (name can be adjusted) so once contributors are comfortable they can do more serious coding/problem solving on a project they are familiar with
* {{done|}} Monthly review of mentored bugs and projects

=== Web Engineering ===
'''Crash stats'''
* {{ok|}} Prototype service for identifying post-crash user actions
* {{done|}} Hardware and performance tuning for new primary data store
* {{ok|}} Remove older, redundant crash storage format from database
* {{drop|}} Improve search performance and features
** API changes in the underlying tech made this much more complicated that originally estimated. Will be carried over to next Q.
* {{done|}} Replace interfaces to deprecated external data sources
* {{done|}} Remove barriers to community installations
'''FHR'''
* {{done|}} Support search diversion plan
'''DXR'''
* {{done|}} Improve infrastructure.
** Switched back end to Elasticsearch, paving the way for [https://wiki.mozilla.org/DXR_Parallel_Tree_Indexing concurrent, independent tree indexing].
** Completely new plugin API supporting multiple languages, multi-core indexing, request-time analysis, binary file handling, and plugins living outside the DXR source tree
* {{ok|}} Broaden our audience.
** Added indexing for several releng trees.
** Basic JS analysis 75% done. Rust analysis in progress.
** Rewrote developer documentation (dxr.readthedocs.org), bringing in about 2 new contributors per week.
** Add macro and typedef direct search.
'''l10n'''
* {{done|}} Get l10n build logs into a searchable data store
* {{miss|}} Replace some buildbot functionality with a10n automation
** a10n work got pushed out because of firefighting to unblock other goals. Estimated 3 weeks away. Will carry over
'''Air Mozilla'''
* {{done|}} Prototype support for streaming media boxes
* {{done|}} Improve desktop user experience

[https://etherpad.mozilla.org/webeng-q32014 full list]

=== SUMO and Input ===
* {{done|}} SUMO: Launch new offline SUMO app [Get Firefox on a Growth Trajectory]
* {{done|}} SUMO: Develop new Community Hub to a level where it can replace legacy Karma app [Enable Communities with Impact]
* {{done|}} SUMO: Research and prototype new experimental features (e.g. geotargeting, Instant Search, Search Suggestions) [Get Firefox on a Growth Trajectory]

* {{done|}} Input: Improve documentation and install to lower the bar for contribution ([[Firefox/Input/Reduce Contributor Pain]]) [Enable Communities with Impact]
* {{done|}} Input: Support Heartbeat ([[Firefox/Input/Heartbeat]]) [Get Firefox on a Growth Trajectory]
* {{risk|}} Input: Dashboards for Everyone ([[Firefox/Input/Dashboards for Everyone]]) [Get Firefox on a Growth Trajectory] (half-done, just needs finishing work, but that keeps getting bumped by high-priority must-be-done-now stuff; think I can finish by october 10th)

=== Release Engineering - Laura ===
* {{drop|}} Enable capacity expansion for bare-metal releng OS X build and test slaves via hardware provided by third-party datacenters (Get Firefox on a Trajectory of Growth) - dropped early on. Third parties are not "there yet" and cost more.
* {{done|}} Simplify release engineering mobile hardware infrastructure (Get Firefox on a Trajectory of Growth)
* {{miss|}} Automate developer access to continuous integration resources to expedite debugging and standing up new job variants. (Enable Communities With Impact) - Progressed a lot. Almost ready for releng to use internally.
* {{done|}} Help enable video operability on the web by providing continuous integration for Cisco Open H.264 builds. (Get Firefox on a Trajectory of Growth)

=== Release Engineering - Taras ===
* {{done|}} Replace aging Firefox update service with a scalable, modern solution. (Get Firefox on a Trajectory of Growth) - Now on beta channel. release channel in early Q4
* {{miss|}} Simplify developer workflow by automating patch landing and uplift. (Enable Communities With Impact) - Implementation done; needs secreview and final integration, deployment.
* {{done|}} Optimize network transfers for build/test automation between datacenters. (Enable Communities With Impact)
* {{miss|}} Continue AWS cost optimizations: EBS < 3% of AWS bill (vs 30% in Q2) (Enable Communities With Impact) - Missed primarily due to lost headcount. Reduced our EBS cost in September to 11% of total; more reductions to come in Q4.
* {{drop|}} Improve developer workflow by migrating 80% of FirefoxOS build/test jobs to taskcluster (Enable Communities With Impact) - this goal is now with jlal in FirefoxOS
* {{drop|}} Turn telemetry into a general purpose s3 ingester and analysis tool - this goal is now with mreid in Services

=== Release Engineering Operations ===
* Build/Test System Performance Enhancements
** {{drop| Unify releng platform architecture, using common tools and best practices, to decrease complexity and enable smoother developer engagement {{bug|1026110}} [Get Firefox on a Trajectory of Growth, Enable Communities With Impact] - blocked on obtaining necessary resources from other groups }}
** {{done| Improve communication and response time for releng network flow requests {{bug|1026112}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{done| Improve security for all releng windows infrastructure {{bug|893716}} [Get Firefox on a Trajectory of Growth] }}
** {{done| Update windows platform developer tools {{bug|1019165}} [Get Firefox on a Trajectory of Growth] }}
* Build/Test System Self-Serve Re-architecture
** {{done| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] - POC created, and openstack was deemed too buggy in its current unreleased state to be production ready }}
** {{drop| Create self-service capability for releng hardware Firefox linux test slaves (build slaves as a stretch goal) {{bug|1026687}} (depends on completion of previous goal) [Get Firefox on a Trajectory of Growth, Scale Firefox OS] - bare metal openstack is proving to be too bleeding edge and buggy to use for production services. We will track changes made in the openstack code base and revist this in 9mo, but we will not move any services to production in FY2014 }}

=== Developer Services ===
* {{done|(with B-team) roll out phase 2 of new review tooling}} [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{done|Upgrade existing Mercurial infrastructure to support more rapid, safe, and coordinated deployment of updates.}} [Get Firefox on a Growth Trajectory / Enable communities with impact]

[https://etherpad.mozilla.org/devservices-Q32014 Full List]

=== Security & Privacy Engineering ===
More details here: [[SecurityEngineering/2014/Q3Goals]]

'''Content Security'''
* {{done|Gecko Security Hooks: Finish code and debugging for NS_NewChannel API, start getting reviews}} (dri=tanvi)
* {{defer|Gecko Security Hooks: Create plan for addon compatibility -- doesn't make sense until New Channel API is done, deferring to next quarter when shimming the JS API for creating new channels}} (dri=tanvi)
* {{done|CSP: Remove old JS implementation from mozilla-central}} (dri=sstamm)
* {{done|Evangelism: Security blog post about new CSP implementation, maybe again as brown bag.}} (dri=sstamm)
* {{miss|''[stretch goal]'' CSP: Fix majority of CSP 1.1 compatibility bugs}}. Couldn't stretch. (dri=ckerschb)

'''Tracking Protection'''
* {{miss|Referer: Finish implementation of <meta> referrer control with volunteer help}}. Unexpected dependencies, will finish about two weeks late. (dri=sstamm)
* {{done|Land first implementation of protection in Fx 33/34 off by default. BONUS: landed frontend code too}} (dri=mmc)

'''Communications Security'''
* {{done|SSL Error Reporting finish first implementation of ssl error reporting feature.}} (dri=grobinson)
* {{ok| HPKP - implement pinning http header}} (dri=cviecco)
* {{done| Update [[CA:RevocationPlan|roadmap for Cert Revocation improvements]]}} (dri=rbarnes)
* {{done| Create a mechanism to provision phones with an alternate cert}} (dri=mgoodwin)
* {{done| Add measurement/enforcement of compliance with CABF Baseline Requirements}} (dri=keeler)
* {{done| Create a tool for testing CA certificate compliance and EV-readiness}} (dri=keeler)
* {{risk| Add support for key wrap/unwrap and ECC in WebCrypto}} (dri=rbarnes)
* {{defer| ''[stretch goal]'' Get CA Program data into one database}} (dri=kathleen)
* {{done| ''[stretch goal]'' Retire first batch of 1024-bit roots, working towards requiring 2048-bit keys for built-in root certificates}} (dri=kathleen)

=== Firefox and Platform Security ===

* {{done|[https://mana.mozilla.org/wiki/display/~gkwong@mozilla.com/Marifuzz Marifuzz ] fuzzer ported to and running on Flame devices.}}
* {{done|Update ASan and LSan work for DOMFuzzer}}
* Update "Bounty Stars" document with issues found by external reporters and updating DOMFuzzer to reflect these results.
* {{done|Get Clang on RelEng ready for official OS X ASan builds.}} - Fuzzing team work is done. Waiting for Releng to update build system.
* {{done|Initial work to move CoreFuzz towards running in cloud environments.}}
* {{done|WebCrypto API fuzzing using Dharma fuzzer.}}
* {{done|Port a portion of WebRTC fuzzing from Frambois fuzzer to Dharma fuzzer.}}
* {{done|Peach: Improving and porting Peach 2 to Python 3.}}
* {{done|Public Mozilla Security Github work: Moving of fuzzing tools from Fuzzing Hg to GitHub, including work to separate harnesses from testcase generation tools.}} - Only outlier is DOMFuzz because of Releng integration.

=== Games Program ===
* {{done| Reach out to 3rd party engines en masse (also for Q4)}}
* {{ok| Select a 3D demo for mobile}}
* {{done| Pick a partner demo to optimize for mobile}}
* {{ok| Focus on supporting shipping games and maintaining platform stability }}
* {{ok| Focus on Shared Array Buffer implementation }}
* {{risk| WebGL Benchmarks}}
* {{ok| Continue to work MDN documentation; get Emscripten documentation started }}
* {{ok| GDC and MWC event support plan}}

=== Release Management ===
For full list, see [[Release_Management/Goals/2014Q3#Release_Management_General|Release Management 2014Q3 Goals]].
* Create and document process for Desktop/Mobile feature fast tracking
* {{done|}} Determine future of ESR and how to manage this channel
** https://groups.google.com/forum/#!topic/mozilla.dev.planning/-IQWXs_zEp8
* {{done|}} Continue desktop throttling experiment with intention of reducing throttled time while maintaining existing level of feedback
** Throttling time currently reduced from 10 to 7 days. Experimenting with further reductions.
* Improve release notes with revamped template for all products
* Create B2G release model proposals and gather feedback for potential changes
* Figure out what to do with B2G Security Releases

===Program Management===

See this wiki page for a full list of [https://wiki.mozilla.org/Program_Management/Firefox/2014-Q3-Goals Program Management goals].

* {{ok|Create a set of dashboards based on the ES database to track platform projects and surface bottlenecks.}}
** Narrowed focus to a set of dashboards for review queues for individuals and teams.
* {{risk|Brown bag presentation/restropective on the agile processes we are using on Desktop and FirefoxOS}}
** With the reorg, revisiting the purpose/target. Might change this goal slightly. Still probably worthwhile planning a brown bag to talk about Desktop process and introduce Trello planning tool for Platform.
* {{ok|Evaluate and produce a report on several tools for helping organize and visualize team backlogs and priority lists; wiki, spreadsheets, Trello, Kanbanize}}
** Using a Trello board for Platform work. Jenn piloting Kanban board for Desktop/Android. Should have a summary, write-up ready by end of Sept.

=== Quality Engineering ===
See this wiki for the full list of [https://wiki.mozilla.org/QA/Goals/2014q3 Quality goals]. What follows are our brief summary of our internal improvement goals for each strategic team.
* Firefox QA - Revitalize our Quality Engineering strategy by switching to a feature-based test strategy for all Firefox browser products so that there are test plans for each feature and testing is executed within two sprints of the feature's code landing
* Firefox OS - Better metrics for quality analysis, provide opportunities for community contribution, and expanding the role of our on-device automation for reporting to Treeherder.
* Services - Ensure new offerings have 98% uptime (FxA Sync, OAuth, FMD, Loop) and no more than 2 P1 bugs discovered post launch while building a core contributor base in services
* Marketplace - Ensure Marketplace's new payments backend, in-app payments, and the Marketplace feed land with high quality releases.
* Platform QA - Deploy into continuous integration a regression testing system for WebRTC along three areas of investigation: 1. "Smoke" tests, 2. Connection tests, and 3. Connection quality tests. These will be performed in a variety of environments, including various network topologies with various performance characteristics, connections between various versions of Firefox, and connections on multiple OS platforms. Test plans will be developed, and we will measure coverage of test plans. Results will be posted and available in Treeherder. We will also build backlog for next Platform Tiger Team tasks.
* Community - Increase conversion of interested and casual contributors to help them become active contributors with strong ties to the QA community

Platform/2014-Q3-Goals

2014-09-23T14:49:51Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
Items marked [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 here] with release 33 and 34 are part of the Q3 landings.

=== Layout ===
* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Enable Vertical Text for major use cases for Chinese & Japanese
** {{miss|{{bug|145503}}}} - Meta Bug. We've made lots of progress, but our big bug won't get closed until Q4
** {{done|{{bug|789096}}}} - Layout with horizontal block flow and vertical text flow
** {{ok|{{bug|902762}}}} - Vertical text run creation
** {{risk|{{bug|1062963}}}} - Make nsFloatManager use logical coordinates

* Text Performance
** We'll get 1 of the 3 we wanted to hit.
** {{ok|{{bug|998869}}}} Streamline parsing of fontlists and improve efficiency of font matching code (note: unicode-range support will fall out of this work)
** {{miss|{{bug|934770}}}} - slow at rendering large blocks of plain text
** {{miss|{{bug|860492}}}} - Divide large text runs into smaller runs to avoid chrome hangs

* Improve Restyling Performance
** {{done|{{bug|977991}}}}
** {{done|{{bug|931668}}}} - (not originally listed for this quarter, but carryover from previous)

* {{drop|Font Inflation and Reflow-on-Zoom }}
** We picked up scrolling features/fixes in Q3 and deferred this item
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* ImageLib
** {{ok|RasterImage for multiple images}}
*** {{done|prerequisite draw API refactoring}} {{bug|1043560}}
*** {{done|store imgFrame objects in the imagelib SurfaceCache}} {{bug|1054079}}
*** {{done|use #1: HQ scaled frames in the surface cache}} {{bug|1060200}}
*** {{ok|use #2: store multiple decode options in surface cache for non-animated images}}
*** {{risk|use #3: store multiple decode options in surface cache for animated images}}

* CSS Projects with Adobe
** {{done|CSS Filters}}

* Animations & Transitions
** {{risk|transitions/animations spec editing}}
** {{risk|transitions refactoring to match new spec}}
*** {{done|{{bug|996796}}}} landed, but work is ongoing for {{bug|960465}}
** {{done|frame reconstruction (625289)}}
** {{risk|Effective start of CSS animations and transitions {{bug|927349}}}}
*** may spill into Q4

* OMTA on non-B2G Platforms (980770)
** {{risk|fix correctness bugs (cascading, etc.)}}
*** partly done in {{bug|996796}}, but cascading fix likely miss
** {{risk|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{done|Get basic implementation of GetAnimationPlayers {{bug|1032573}}}}
** {{risk|Implement PlaybackControl() {{bug|1033114}}}}
*** may spill into Q4

* CSS Scrolling
** {{ok|CSS scroll snapping}}
** {{ok|scroll-behavior:smooth}}

* CSS Flexbox
** {{ok|performance bugs}}
*** significant improvement on {{bug|946167}}, though more to do
** {{ok|spec changes}}
*** completed {{bug|984711}}/{{bug|1037177}}/{{bug|1015474}} on min-width/height: auto
*** completed {{bug|1032922}} and followups on flex-basis: main-size rename
*** abs-pos handling at-risk (picked up object-fit/position instead)

* CSS Ruby
** Our intern got through a bunch of this, but we'll continue it next quarter; remaining work tracked in {{bug|css-ruby}} and {{bug|enable-css-ruby}}
** {{done|style system support}}
** {{done|frame construction}}
** {{done|anonymous box handling}}
** {{done|reflow architecture and horizontal positioning}}
** {{miss|line breaking}}
** {{miss|vertical positioning}}
** {{miss|other dependencies on enabling the feature}}

=== Media ===
* {{miss|Enable YouTube MSE/VP9 for Firefox 33 in Nightly/Aurora {{bug|1000686}}}}
* {{miss|Enable YouTube MSE/MP4 on Windows and Firefox OS for Firefox 34}}

'''Detailed Breakdown'''
* MSE Common
** {{done|Rate adaption/buffer switching, reseting}}
** {{miss|Seeking into unbuffered ranges {{bug|1056440}}}}
** {{todo|Eviction/pinning}}
* MSE WebM
** {{done|WebM segment parser {{bug|881512}}{{bug|1044498}}}}
* MSE MP4
** {{done|MP4 segment parser {{bug|1027875}}{{bug|1057203}}}}
** MP4 Demuxer
*** {{done|Integrate stagefright MP4 demuxer {{bug|908503}}}}
*** {{done|Accurate range reporting {{bug|1045909}}}}
*** {{done|CENC support {{bug|1022434}}}}
*** {{todo|DASHIF and other players aside from YouTube {{bug|1039149}}}}
** H.264/AAC Decoder
*** {{done|MP4/fMP4 platform decoder module for Mac OSX {{bug|941296}}}}
*** {{miss|MP4 support on Firefox OS {{bug|1060900}}}}
**** {{done|MP4 platform decoder module for Firefox OS {{bug|941302}}}}
**** {{miss|Use a single shared decoder for MSE on b2g {{bug|1036849}}}}

=== DOM ===
* {{ok|Mirror prototype of DOM objects through xray wrappers ({{bug|787070}}, peterv)}}
* {{risk|Remove nsDOMClassInfo.cpp}}
** Given the recent focus on e10s, we may not get through all of this work this quarter.
* {{done|Make less-privileged non-Xrayable unwaived opaque from privileged code (bholley, {{bug|856067}})}}
* {{done|Route all JSContext pushing through AutoJSAPI and Implement GetEntryGlobal (bobowen, bholley, {{bug|951991}})}}
* {{ok|Land <picture> preffed on on nightly ({{bug|1017875}}) (johns)}}
* {{done|audit callsites of IsInDoc()/GetCurrentDoc to ensure correct Shadow DOM behaviour and fix Shadow DOM blockers for Gaia (smaug, wchen) ({{bug|1026047}})}}
* {{risk|land Service Workers preffed off on nightly (nsm, bkelly, baku) ({{bug|903441}})}}
** This is progressing well, but won't be *done* until the end of the quarter, so still on track.
** Note that originally we thought things would be at the point where Gecko and Blink would be far enough along with a stable spec that this could be preffed on. That is not going to be the case but we are still aiming to have a usable implementation preffed off.
** There remain spec questions about Cache which have impacted the design of our implementation.

=== WebAPI ===
* {{ok|create design plan for "share" activity (flow, what kind of objects are involved) (annevk)}}
* {{ok|document existing activities usage in gaia (ehsan)}}
* {{ok|get [https://w3c.github.io/screen-orientation/ screen orientation spec] to LC (marcosc)}}
* {{done|publish [http://www.w3.org/TR/wake-lock-use-cases/ use cases for wake locks] (marcosc)}}
* {{ok|publish spec for [http://w3c.github.io/wake-lock/ "wakelock" API] (marcosc)}}
* {{done|24/12 hour format API (ehsan) {{bug|903683}}}}
* {{ok|{{bug|942542}} new quota API on PBackground for Service Worker cache (janv)}}
* {{ok|{{bug|701634}} IndexedDB in workers (bent)}}

=== JS ===
* {{miss|ES6 classes: }}{{Bug|837314}}
* {{jok|1020751}} Generational GC on Firefox OS
* {{jok|650161}} Compacting GC to reduce memory usage
* {{jok|856533}} Escape analysis JIT optimizations
* {{done|Use Latin1 strings to reduce memory usage: }}{{Bug|998392}}
* {{jok|903519}} Allocate strings in GC nursery (for performance)
* {{miss|ARM64 JIT ''[stretch goal]'': }} {{Bug|972710}}

=== Accessibility ===
* {{risk|}}e10s: proxy the common a11y API stuff like name, role, and states.
* {{done|}}GAIA: Fix [https://bugzilla.mozilla.org/buglist.cgi?priority=--&f1=blocked&list_id=10674217&o1=anyexact&resolution=---&query_based_on=b2ga11y%20p%3D1&o2=substring&query_format=advanced&f2=status_whiteboard&v1=893789&component=Disability%20Access%20APIs&component=Gaia&component=Gaia%3A%3ABluetooth%20File%20Transfer&component=Gaia%3A%3ABrowser&component=Gaia%3A%3ABuild&component=Gaia%3A%3ACalendar&component=Gaia%3A%3ACamera&component=Gaia%3A%3AClock&component=Gaia%3A%3AContacts&component=Gaia%3A%3ACost%20Control&component=Gaia%3A%3ADialer&component=Gaia%3A%3AE-Mail&component=Gaia%3A%3AEverything.me&component=Gaia%3A%3AFirst%20Time%20Experience&component=Gaia%3A%3AFMRadio&component=Gaia%3A%3AGallery&component=Gaia%3A%3AGithubBot&component=Gaia%3A%3AHomescreen&component=Gaia%3A%3AKeyboard&component=Gaia%3A%3AL10n&component=Gaia%3A%3ALoop&component=Gaia%3A%3AMusic&component=Gaia%3A%3ANotes&component=Gaia%3A%3APDF%20Viewer&component=Gaia%3A%3APerformanceTest&component=Gaia%3A%3ARingtones&component=Gaia%3A%3ASearch&component=Gaia%3A%3ASettings&component=Gaia%3A%3ASMS&component=Gaia%3A%3ASystem&component=Gaia%3A%3ASystem%3A%3ABrowser%20Chrome&component=Gaia%3A%3ASystem%3A%3AInput%20Mgmt&component=Gaia%3A%3ASystem%3A%3ALockscreen&component=Gaia%3A%3ASystem%3A%3AWindow%20Mgmt&component=Gaia%3A%3ATestAgent&component=Gaia%3A%3AUI%20Tests&component=Gaia%3A%3AVideo&component=Gaia%3A%3AWallpaper&component=Gaia%3A%3AWappush&v2=b2ga11y%20p%3D1&product=Core&product=Firefox%20OS all Gaia P1 a11y bugs] (~30 at this time).
** 49 (all) are fixed.
* {{done|}}FFOS: {{Bug|1030465}} - Volume change should update the screen reader volume.
* {{done|}}FFOS: {{Bug|1030466}} - Headphones screen reader volume is too low.
* {{done|}}FFOS: {{Bug|1030468}} - VC rectangle needs to work with scaled content.
* {{done|}}FFOS: {{Bug|1030470}} - Localization needs to work when switching locales in FxOS.

=== Perf ===

Fix major source of browser jank:

* {{ok|Initialize plugin instances asynchronously {{bug|998863}} }}
* {{ok|Pause heavy main-thread activities while user is interacting with the browser: }}
** {{ok|Determine when a user is actively interacting with the browser}}
** {{ok|Detect when jank occurs during interactions and report to Telemetry {{bug|1017055}} }}
** {{ok|Experiment with hinting to GC & CC that they should pause while the user is interacting with the browser}}
* {{ok|Help Frontend team with Places refactoring, eliminate some of the [http://telemetry.mozilla.org/slowsql/ Places main-thread SQL] reported to Telemetry }}
* {{ok|Don't store UI customization in localstore.rdf, use off-main thread JSON instead {{bug|559505}} }}

Improve Firefox startup (identified as a top issue in user research):

* {{ok|Reduce appearance of the "profile is in use" message on startup {{bug|286355}} }}
* {{ok|Restore windows one by one during session-restore {{bug|1034534}} and/or load windows by descending z-order {{bug|1034036}} }}
* {{ok|C++ version of AsyncShutdown {{bug|918317}} }}

Prevent performance regressions:

* {{ok|Implement automatic detection & alerting for Telemetry regressions {{bug|1031032}} }}
* {{ok|Help developers understand & diagnose Talos regressions}}, e.g. [https://bugzilla.mozilla.org/show_bug.cgi?id=1026550 Firefox 33 regression tracking], [https://bugzilla.mozilla.org/show_bug.cgi?id=1004427 Firefox 32 regressions], [https://bugzilla.mozilla.org/show_bug.cgi?id=990085 Firefox 31]

Grow community:

* {{ok|Mentor at least 5 external contributors}}

=== Networking ===

* {{ok|Ship Network Predictor ("Seer") on nightly, using HTTP cache instead of SQLite ({{bug|1009122}}) (hurley)}}
* {{done|Ship current (hopefully final) IETF version of HTTP/2 preffed on in nightly (hurley)}}
* {{ok|HTTP/2 "alt-svc" support ({{bug|1003448}}) (mcmanus)}}
* {{drop|HTTP cache: determine if revalidation is needed w/o doing I/O ({{bug|983122}}) (sworkman) }}
* {{ok|Network up/down link detection on all platforms ({{bug|939318}}) (bagder) }}
* {{drop|Implement WebSocket compression extension ({{bug|792831}}) (michal) }}

=== Mobile ===

=== A*Team ===

For full list, see [[Auto-tools/Goals/2014Q3|A-Team Goals 2014Q3]]

'''B2G'''
* {{ok|}} Run a set of performance and correctness tests per-commit to b2g-inbound on Flame devices
* {{ok|}} Get gaia-integration tests running on device
* {{ok|}} Expand the FxOS Certification Suite with 1.4 support, test automation to prevent regressions, and investigation of support for non-phone devices
* {{ok|}} Green up B2G tests on TaskCluster (joint with RelEng)

'''Developer Productivity'''
* {{ok|}} Deploy ReviewBoard for developers to start using (joint with RelEng)

'''Performance'''
* {{ok|}} Deploy new Talos tests for tp5o_scroll, webgl, webrtc, and mainthread I/O
* {{ok|}} Get Datazilla alerts to beta mode (full parity with graph server alerts) with reduced noise
* {{ok|}} Get Eideticker running against Android again with increased frequency
* {{ok|}} Run B2G Eideticker against same branch/build combinations as our other on-device perf tests
* {{ok|}} Stand up a Games Benchmarking system for webaudio tests running against Firefox and Chrome

'''Treeherder'''
* {{ok|}} Deliver performance web service for ingesting and returning performance data
* {{ok|}} Deliver a UI for viewing Talos data

'''Sheriffing'''
* {{ok|}} Fully transition sheriffing from TBPL to Treeherder

'''General Automation'''
* {{ok|}} Create weekly reports that describe how many tests have been added/disabled/enabled per suite and platform
* {{ok|}} Move reftest to mozbase
* {{ok|}} Add command executors for Marionette for Java and Python

'''Bugzilla'''
* {{done|}} Improve load time of related bugs; can decrease show_bug load times by up to 12%
* {{ok|}} Minify and concatenate JS files
* {{ok|}} Authoritative view for review history
* {{ok|}} Rewrite docs for REST API

'''Community'''
* {{ok|}} Create good_next_bugs (name can be adjusted) so once contributors are comfortable they can do more serious coding/problem solving on a project they are familiar with
* {{ok|}} Monthly review of mentored bugs and projects

=== Web Engineering ===
'''Crash stats'''
* {{ok|}} Prototype service for identifying post-crash user actions
* {{done|}} Hardware and performance tuning for new primary data store
* {{ok|}} Remove older, redundant crash storage format from database
* {{drop|}} Improve search performance and features
* {{done|}} Replace interfaces to deprecated external data sources
* {{done|}} Remove barriers to community installations
'''FHR'''
* {{done|}} Support search diversion plan
'''DXR'''
* {{ok|}} Improve infrastructure.
** For example, switch to ES backend, which will enable us to build multi-language support and parallel tree indexing.
* {{ok|}} Broaden our audience.
** Pull users away from MXR so we can shut it off. For example, add support for Rust or JS, squash MXR migration blockers.
'''l10n'''
* {{ok|}} Get l10n build logs into a searchable data store
* {{ok|}} Replace some buildbot functionality with a10n automation
'''Air Mozilla'''
* {{done|}} Prototype support for streaming media boxes
* {{done|}} Improve desktop user experience

[https://etherpad.mozilla.org/webeng-q32014 full list]

=== SUMO and Input ===
* {{done|}} SUMO: Launch new offline SUMO app [Get Firefox on a Growth Trajectory]
* {{ok|}} SUMO: Develop new Community Hub to a level where it can replace legacy Karma app [Enable Communities with Impact]
* {{ok|}} SUMO: Research and prototype new experimental features (e.g. geotargeting, Instant Search, Search Suggestions) [Get Firefox on a Growth Trajectory]

* {{done|}} Input: Improve documentation and install to lower the bar for contribution [Enable Communities with Impact]
* {{ok|}} Input: Support Heartbeat [Get Firefox on a Growth Trajectory]
* {{ok|}} Input: Dashboards for Everyone [Get Firefox on a Growth Trajectory]

=== Release Engineering - Laura ===
* {{drop|}} Enable capacity expansion for bare-metal releng OS X build and test slaves via hardware provided by third-party datacenters (Get Firefox on a Trajectory of Growth)
* {{ok|}} Simplify release engineering mobile hardware infrastructure (Get Firefox on a Trajectory of Growth)
* {{risk|}} Automate developer access to continuous integration resources to expedite debugging and standing up new job variants. (Enable Communities With Impact)
* {{ok|}} Help enable video operability on the web by providing continuous integration for Cisco Open H.264 builds. (Get Firefox on a Trajectory of Growth)

=== Release Engineering - Taras ===
* {{ok|}} Replace aging Firefox update service with a scalable, modern solution. (Get Firefox on a Trajectory of Growth)
* {{ok|}} Simplify developer workflow by automating patch landing and uplift. (Enable Communities With Impact)
* {{ok|}} Optimize network transfers for build/test automation between datacenters. (Enable Communities With Impact)
* {{ok|}} Continue AWS cost optimizations: EBS < 3% of AWS bill(vs 30% in Q2) (Enable Communities With Impact)
* {{drop|}} Improve developer workflow by migrating 80% of FirefoxOS build/test jobs to taskcluster (Enable Communities With Impact) - this goal is now with jlal in FirefoxOS
* {{drop|}} Turn telemetry into a general purpose s3 ingester and analysis tool - this goal is now with mreid in Services

=== Release Engineering Operations ===
* Build/Test System Performance Enhancements
** {{drop| Unify releng platform architecture, using common tools and best practices, to decrease complexity and enable smoother developer engagement {{bug|1026110}} [Get Firefox on a Trajectory of Growth, Enable Communities With Impact] - blocked on obtaining necessary resources from other groups }}
** {{done| Improve communication and response time for releng network flow requests {{bug|1026112}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{ok| Improve security for all releng windows infrastructure {{bug|893716}} [Get Firefox on a Trajectory of Growth] }}
** {{done| Update windows platform developer tools {{bug|1019165}} [Get Firefox on a Trajectory of Growth] }}
* Build/Test System Self-Serve Re-architecture
** {{done| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] - POC created, and openstack was deemed too buggy in its current unreleased state to be production ready }}
** {{drop| Create self-service capability for releng hardware Firefox linux test slaves (build slaves as a stretch goal) {{bug|1026687}} (depends on completion of previous goal) [Get Firefox on a Trajectory of Growth, Scale Firefox OS] - bare metal openstack is proving to be too bleeding edge and buggy to use for production services. We will continue to work on R&D for this project and track changes made in the openstack code base, but we will not move any services to production in FY2014 }}

=== Developer Services ===
* {{done|(with B-team) roll out phase 2 of new review tooling}} [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{new|Upgrade existing Mercurial infrastructure to support more rapid, safe, and coordinated deployment of updates.}} [Get Firefox on a Growth Trajectory / Enable communities with impact]

[https://etherpad.mozilla.org/devservices-Q32014 Full List]

=== Security & Privacy Engineering ===
More details here: [[SecurityEngineering/2014/Q3Goals]]

'''Content Security'''
* {{done|Gecko Security Hooks: Finish code and debugging for NS_NewChannel API, start getting reviews}} (dri=tanvi)
* {{defer|Gecko Security Hooks: Create plan for addon compatibility -- doesn't make sense until New Channel API is done, deferring to next quarter when shimming the JS API for creating new channels}} (dri=tanvi)
* {{done|CSP: Remove old JS implementation from mozilla-central}} (dri=sstamm)
* {{done|Evangelism: Security blog post about new CSP implementation, maybe again as brown bag.}} (dri=sstamm)
* {{ok|''[stretch goal]'' CSP: Fix majority of CSP 1.1 compatibility bugs}} (dri=ckerschb)

'''Tracking Protection'''
* {{ok|Referer: Finish implementation of <meta> referrer control with volunteer help}} (dri=sstamm)
* {{done|Land first implementation of protection in Fx 33/34 off by default. BONUS: landed frontend code too}} (dri=mmc)

'''Communications Security'''
* {{ok|SSL Error Reporting finish first implementation of ssl error reporting feature.}} (dri=grobinson)
* {{ok| HPKP - implement pinning http header}} (dri=cviecco)
* {{done| Update [[CA:RevocationPlan|roadmap for Cert Revocation improvements]]}} (dri=rbarnes)
* {{done| Create a mechanism to provision phones with an alternate cert}} (dri=mgoodwin)
* {{done| Add measurement/enforcement of compliance with CABF Baseline Requirements}} (dri=keeler)
* {{done| Create a tool for testing CA certificate compliance and EV-readiness}} (dri=keeler)
* {{ok| Add support for key wrap/unwrap and ECC in WebCrypto}} (dri=rbarnes)
* {{ok| ''[stretch goal]'' Get CA Program data into one database}} (dri=kathleen)
* {{done| ''[stretch goal]'' Retire first batch of 1024-bit roots, working towards requiring 2048-bit keys for built-in root certificates}} (dri=kathleen)

=== Firefox and Platform Security ===

* [https://mana.mozilla.org/wiki/display/~gkwong@mozilla.com/Marifuzz Marifuzz ] fuzzer ported to and running on Flame devices.
* Update ASan and LSan work for DOMFuzzer
* Update "Bounty Stars" document with issues found by external reporters and updating DOMFuzzer to reflect these results.
* Get Clang on RelEng ready for official OS X ASan builds.
* Initial work to move CoreFuzz towards running in cloud environments.
* WebCrypto API fuzzing using Dharma fuzzer.
* Port a portion of WebRTC fuzzing from Frambois fuzzer to Dharma fuzzer.
* Peach: Improving and porting Peach 2 to Python 3.
* Public Mozilla Security Github work: Moving of fuzzing tools from Fuzzing Hg to GitHub, including work to separate harnesses from testcase generation tools.

=== Games Program ===
* {{done| Reach out to 3rd party engines en masse (also for Q4)}}
* {{ok| Select a 3D demo for mobile}}
* {{done| Pick a partner demo to optimize for mobile}}
* {{ok| Focus on supporting shipping games and maintaining platform stability }}
* {{ok| Focus on Shared Array Buffer implementation }}
* {{risk| WebGL Benchmarks}}
* {{ok| Continue to work MDN documentation; get Emscripten documentation started }}
* {{ok| GDC and MWC event support plan}}

=== Release Management ===
For full list, see [[Release_Management/Goals/2014Q3#Release_Management_General|Release Management 2014Q3 Goals]].
* Create and document process for Desktop/Mobile feature fast tracking
* {{done|}} Determine future of ESR and how to manage this channel
** https://groups.google.com/forum/#!topic/mozilla.dev.planning/-IQWXs_zEp8
* {{done|}} Continue desktop throttling experiment with intention of reducing throttled time while maintaining existing level of feedback
** Throttling time currently reduced from 10 to 7 days. Experimenting with further reductions.
* Improve release notes with revamped template for all products
* Create B2G release model proposals and gather feedback for potential changes
* Figure out what to do with B2G Security Releases

===Program Management===

See this wiki page for a full list of [https://wiki.mozilla.org/Program_Management/Firefox/2014-Q3-Goals Program Management goals].

* {{ok|Create a set of dashboards based on the ES database to track platform projects and surface bottlenecks.}}
** Narrowed focus to a set of dashboards for review queues for individuals and teams.
* {{risk|Brown bag presentation/restropective on the agile processes we are using on Desktop and FirefoxOS}}
** With the reorg, revisiting the purpose/target. Might change this goal slightly. Still probably worthwhile planning a brown bag to talk about Desktop process and introduce Trello planning tool for Platform.
* {{ok|Evaluate and produce a report on several tools for helping organize and visualize team backlogs and priority lists; wiki, spreadsheets, Trello, Kanbanize}}
** Using a Trello board for Platform work. Jenn piloting Kanban board for Desktop/Android. Should have a summary, write-up ready by end of Sept.

=== Quality Engineering ===
See this wiki for the full list of [https://wiki.mozilla.org/QA/Goals/2014q3 Quality goals]. What follows are our brief summary of our internal improvement goals for each strategic team.
* Firefox QA - Revitalize our Quality Engineering strategy by switching to a feature-based test strategy for all Firefox browser products so that there are test plans for each feature and testing is executed within two sprints of the feature's code landing
* Firefox OS - Better metrics for quality analysis, provide opportunities for community contribution, and expanding the role of our on-device automation for reporting to Treeherder.
* Services - Ensure new offerings have 98% uptime (FxA Sync, OAuth, FMD, Loop) and no more than 2 P1 bugs discovered post launch while building a core contributor base in services
* Marketplace - Ensure Marketplace's new payments backend, in-app payments, and the Marketplace feed land with high quality releases.
* Platform QA - Deploy into continuous integration a regression testing system for WebRTC along three areas of investigation: 1. "Smoke" tests, 2. Connection tests, and 3. Connection quality tests. These will be performed in a variety of environments, including various network topologies with various performance characteristics, connections between various versions of Firefox, and connections on multiple OS platforms. Test plans will be developed, and we will measure coverage of test plans. Results will be posted and available in Treeherder. We will also build backlog for next Platform Tiger Team tasks.
* Community - Increase conversion of interested and casual contributors to help them become active contributors with strong ties to the QA community

Platform/2014-Q3-Goals

2014-08-25T16:30:28Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
Items marked [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 here] with release 33 and 34 are part of the Q3 landings.

=== Layout ===
* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Enable Vertical Text for major use cases for Chinese & Japanese
** {{ok|bug 145503}}

* Text Performance
** {{ok|{{bug|998869}}}} Streamline parsing of fontlists and improve efficiency of font matching code (note: unicode-range support will fall out of this work)
** {{ok|{{bug|934770}}}} - slow at rendering large blocks of plain text
** {{ok|{{bug|860492}}}} - Divide large text runs into smaller runs to avoid chrome hangs

* Improve Restyling Performance
** {{ok|bug 977991}}

* {{ok|Font Inflation and Reflow-on-Zoom }}
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Projects with Adobe
** {{ok|CSS Filters}}

* Animations & Transitions
** {{ok|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{ok|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|TBD}}

* CSS Scrolling
** {{ok|CSS scroll snapping}}
** {{ok|scroll-behavior:smooth}}

* CSS Flexbox
** {{ok|performance bugs}}
** {{ok|spec changes}}

* CSS Ruby
** {{ok|implementation}}

=== Media ===
* {{ok|Enable MSE/VP9 for Firefox 33 in Nightly/Aurora}}
* {{ok|Enable MSE/MP4 on Windows and Firefox OS for Firefox 34}}

=== DOM ===
* {{ok|Mirror prototype of DOM objects through xray wrappers (peterv)}}
* {{ok|Remove nsDOMClassInfo.cpp}}
* {{done|Make less-privileged non-Xrayable unwaived opaque from privileged code (bholley, {{bug|856067}})}}
* {{done|Route all JSContext pushing through AutoJSAPI and Implement GetEntryGlobal (bobowen, bholley, {{bug|951991}})}}
* {{ok|Land <picture> preffed on on nightly ({{bug|1017875}}) (johns)}}
* {{ok|audit callsites of IsInDoc()/GetCurrentDoc to ensure correct Shadow DOM behaviour and fix Shadow DOM blockers for Gaia (smaug, wchen) ({{bug|1026047}})}}
* {{ok|land Service Workers preffed on on nightly (nsm, bkelly, baku) ({{bug|903441}})}}

=== WebAPI ===
* {{ok|create design plan for "share" activity (flow, what kind of objects are involved) (annevk)}}
* {{ok|document existing activities usage in gaia (ehsan)}}
* {{ok|get [https://w3c.github.io/screen-orientation/ screen orientation spec] to LC (marcosc)}}
* {{ok|publish use cases and spec for [http://w3c.github.io/screen-wake/ "wakelock" API] (marcosc)}}
* {{ok|24/12 hour format API (ehsan) {{bug|903683}}}}
* {{ok|{{bug|942542}} new quota API on PBackground for Service Worker cache (janv)}}
* {{ok|{{bug|701634}} IndexedDB in workers (bent)}}

=== JS ===
* {{jok|837314}} ES6 classes
* {{jok|941796}} Generational GC on Firefox OS
* {{jok|650161}} Compacting GC to reduce memory usage
* {{jok|856533}} Escape analysis JIT optimizations
* {{jok|998392}} Use Latin1 strings to reduce memory usage
* {{jok|903519}} Allocate strings in GC nursery (for performance)
* {{jok|972710}} ARM64 JIT ''[stretch goal]''

=== Accessibility ===
* {{ok|}}e10s: proxy the common a11y API stuff like name, role, and states.
* {{ok|}}GAIA: Fix [https://bugzilla.mozilla.org/buglist.cgi?priority=--&f1=blocked&list_id=10674217&o1=anyexact&resolution=---&query_based_on=b2ga11y%20p%3D1&o2=substring&query_format=advanced&f2=status_whiteboard&v1=893789&component=Disability%20Access%20APIs&component=Gaia&component=Gaia%3A%3ABluetooth%20File%20Transfer&component=Gaia%3A%3ABrowser&component=Gaia%3A%3ABuild&component=Gaia%3A%3ACalendar&component=Gaia%3A%3ACamera&component=Gaia%3A%3AClock&component=Gaia%3A%3AContacts&component=Gaia%3A%3ACost%20Control&component=Gaia%3A%3ADialer&component=Gaia%3A%3AE-Mail&component=Gaia%3A%3AEverything.me&component=Gaia%3A%3AFirst%20Time%20Experience&component=Gaia%3A%3AFMRadio&component=Gaia%3A%3AGallery&component=Gaia%3A%3AGithubBot&component=Gaia%3A%3AHomescreen&component=Gaia%3A%3AKeyboard&component=Gaia%3A%3AL10n&component=Gaia%3A%3ALoop&component=Gaia%3A%3AMusic&component=Gaia%3A%3ANotes&component=Gaia%3A%3APDF%20Viewer&component=Gaia%3A%3APerformanceTest&component=Gaia%3A%3ARingtones&component=Gaia%3A%3ASearch&component=Gaia%3A%3ASettings&component=Gaia%3A%3ASMS&component=Gaia%3A%3ASystem&component=Gaia%3A%3ASystem%3A%3ABrowser%20Chrome&component=Gaia%3A%3ASystem%3A%3AInput%20Mgmt&component=Gaia%3A%3ASystem%3A%3ALockscreen&component=Gaia%3A%3ASystem%3A%3AWindow%20Mgmt&component=Gaia%3A%3ATestAgent&component=Gaia%3A%3AUI%20Tests&component=Gaia%3A%3AVideo&component=Gaia%3A%3AWallpaper&component=Gaia%3A%3AWappush&v2=b2ga11y%20p%3D1&product=Core&product=Firefox%20OS all Gaia P1 a11y bugs] (~30 at this time).
* {{done|}}FFOS: {{Bug|1030465}} - Volume change should update the screen reader volume.
* {{done|}}FFOS: {{Bug|1030466}} - Headphones screen reader volume is too low.
* {{ok|}}FFOS: {{Bug|1030468}} - VC rectangle needs to work with scaled content.
* {{done|}}FFOS: {{Bug|1030470}} - Localization needs to work when switching locales in FxOS.

=== Perf ===

Fix major source of browser jank:

* {{ok|Initialize plugin instances asynchronously {{bug|998863}} }}
* {{ok|Pause heavy main-thread activities while user is interacting with the browser: }}
** {{ok|Determine when a user is actively interacting with the browser}}
** {{ok|Detect when jank occurs during interactions and report to Telemetry {{bug|1017055}} }}
** {{ok|Experiment with hinting to GC & CC that they should pause while the user is interacting with the browser}}
* {{ok|Help Frontend team with Places refactoring, eliminate some of the [http://telemetry.mozilla.org/slowsql/ Places main-thread SQL] reported to Telemetry }}
* {{ok|Don't store UI customization in localstore.rdf, use off-main thread JSON instead {{bug|559505}} }}

Improve Firefox startup (identified as a top issue in user research):

* {{ok|Reduce appearance of the "profile is in use" message on startup {{bug|286355}} }}
* {{ok|Restore windows one by one during session-restore {{bug|1034534}} and/or load windows by descending z-order {{bug|1034036}} }}
* {{ok|C++ version of AsyncShutdown {{bug|918317}} }}

Prevent performance regressions:

* {{ok|Implement automatic detection & alerting for Telemetry regressions {{bug|1031032}} }}
* {{ok|Help developers understand & diagnose Talos regressions}}, e.g. [https://bugzilla.mozilla.org/show_bug.cgi?id=1026550 Firefox 33 regression tracking], [https://bugzilla.mozilla.org/show_bug.cgi?id=1004427 Firefox 32 regressions], [https://bugzilla.mozilla.org/show_bug.cgi?id=990085 Firefox 31]

Grow community:

* {{ok|Mentor at least 5 external contributors}}

=== Networking ===

* {{ok|Ship Network Predictor ("Seer") on nightly, using HTTP cache instead of SQLite ({{bug|1009122}}) (hurley)}}
* {{ok|Ship current (hopefully final) IETF version of HTTP/2 preffed on in nightly (hurley)}}
* {{ok|HTTP/2 "alt-svc" support ({{bug|1003448}}) (mcmanus)}}
* {{ok|HTTP cache: determine if revalidation is needed w/o doing I/O ({{bug|983122}}) (sworkman) }}
* {{ok|Network up/down link detection on all platforms ({{bug|939318}}) (bagder) }}
* {{ok|Implement WebSocket compression extension ({{bug|792831}}) (michal) }}

=== Mobile ===

=== A*Team ===

For full list, see [[Auto-tools/Goals/2014Q3|A-Team Goals 2014Q3]]

'''B2G'''
* {{ok|}} Run a set of performance and correctness tests per-commit to b2g-inbound on Flame devices
* {{ok|}} Get gaia-integration tests running on device
* {{ok|}} Expand the FxOS Certification Suite with 1.4 support, test automation to prevent regressions, and investigation of support for non-phone devices
* {{ok|}} Green up B2G tests on TaskCluster (joint with RelEng)

'''Developer Productivity'''
* {{ok|}} Deploy ReviewBoard for developers to start using (joint with RelEng)

'''Performance'''
* {{ok|}} Deploy new Talos tests for tp5o_scroll, webgl, webrtc, and mainthread I/O
* {{ok|}} Get Datazilla alerts to beta mode (full parity with graph server alerts) with reduced noise
* {{ok|}} Get Eideticker running against Android again with increased frequency
* {{ok|}} Run B2G Eideticker against same branch/build combinations as our other on-device perf tests
* {{ok|}} Stand up a Games Benchmarking system for webaudio tests running against Firefox and Chrome

'''Treeherder'''
* {{ok|}} Deliver performance web service for ingesting and returning performance data
* {{ok|}} Deliver a UI for viewing Talos data

'''Sheriffing'''
* {{ok|}} Fully transition sheriffing from TBPL to Treeherder

'''General Automation'''
* {{ok|}} Create weekly reports that describe how many tests have been added/disabled/enabled per suite and platform
* {{ok|}} Move reftest to mozbase
* {{ok|}} Add command executors for Marionette for Java and Python

'''Bugzilla'''
* {{done|}} Improve load time of related bugs; can decrease show_bug load times by up to 12%
* {{ok|}} Minify and concatenate JS files
* {{ok|}} Authoritative view for review history
* {{ok|}} Rewrite docs for REST API

'''Community'''
* {{ok|}} Create good_next_bugs (name can be adjusted) so once contributors are comfortable they can do more serious coding/problem solving on a project they are familiar with
* {{ok|}} Monthly review of mentored bugs and projects

=== Web Engineering ===
'''Crash stats'''
* {{ok|}} Prototype service for identifying post-crash user actions
* {{ok|}} Hardware and performance tuning for new primary data store
* {{ok|}} Remove older, redundant crash storage format from database
* {{ok|}} Improve search performance and features
* {{ok|}} Replace interfaces to deprecated external data sources
* {{ok|}} Remove barriers to community installations
'''FHR'''
* {{ok|}} Support search diversion plan
'''DXR'''
* {{ok|}} Improve infrastructure.
** For example, switch to ES backend, which will enable us to build multi-language support and parallel tree indexing.
* {{ok|}} Broaden our audience.
** Pull users away from MXR so we can shut it off. For example, add support for Rust or JS, squash MXR migration blockers.
'''l10n'''
* {{ok|}} Get l10n build logs into a searchable data store
* {{ok|}} Replace some buildbot functionality with a10n automation
'''Air Mozilla'''
* {{ok|}} Prototype support for streaming media boxes
* {{ok|}} Improve desktop user experience

[https://etherpad.mozilla.org/webeng-q32014 full list]

=== SUMO and Input ===
* {{done|}} SUMO: Launch new offline SUMO app [Get Firefox on a Growth Trajectory]
* {{ok|}} SUMO: Develop new Community Hub to a level where it can replace legacy Karma app [Enable Communities with Impact]
* {{ok|}} SUMO: Research and prototype new experimental features (e.g. geotargeting, Instant Search, Search Suggestions) [Get Firefox on a Growth Trajectory]

* {{done|}} Input: Improve documentation and install to lower the bar for contribution [Enable Communities with Impact]
* {{ok|}} Input: Support Heartbeat [Get Firefox on a Growth Trajectory]
* {{ok|}} Input: Dashboards for Everyone [Get Firefox on a Growth Trajectory]

=== Release Engineering - Laura ===
* {{ok|}} Enable capacity expansion for bare-metal releng OS X build and test slaves via hardware provided by third-party datacenters (Get Firefox on a Trajectory of Growth)
* {{ok|}} Simplify release engineering mobile hardware infrastructure (Get Firefox on a Trajectory of Growth)
* {{ok|}} Automate developer access to continuous integration resources to expedite debugging and standing up new job variants. (Enable Communities With Impact)
* {{ok|}} Help enable video operability on the web by providing continuous integration for Cisco Open H.264 builds. (Get Firefox on a Trajectory of Growth)

=== Release Engineering - Taras ===
* {{ok|}} Replace aging Firefox update service with a scalable, modern solution. (Get Firefox on a Trajectory of Growth)
* {{ok|}} Simplify developer workflow by automating patch landing and uplift. (Enable Communities With Impact)
* {{ok|}} Optimize network transfers for build/test automation between datacenters. (Enable Communities With Impact)
* {{ok|}} Continue AWS cost optimizations: EBS < 3% of AWS bill(vs 30% in Q2) (Enable Communities With Impact)
* {{ok|}} Improve developer workflow by migrating 80% of FirefoxOS build/test jobs to taskcluster (Enable Communities With Impact)
* {{ok|}} Turn telemetry is into a general purpose s3 ingester and analysis tool

=== Release Engineering Operations ===
* Build/Test System Performance Enhancements
** {{drop| Unify releng platform architecture, using common tools and best practices, to decrease complexity and enable smoother developer engagement {{bug|1026110}} [Get Firefox on a Trajectory of Growth, Enable Communities With Impact] - blocked on obtaining necessary resources from other groups }}
** {{ok| Improve communication and response time for releng network flow requests {{bug|1026112}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{ok| Improve security for all releng windows infrastructure {{bug|893716}} [Get Firefox on a Trajectory of Growth] }}
** {{done| Update windows platform developer tools {{bug|1019165}} [Get Firefox on a Trajectory of Growth] }}
* Build/Test System Self-Serve Re-architecture
** {{prev| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{drop| Create self-service capability for releng hardware Firefox linux test slaves (build slaves as a stretch goal) {{bug|1026687}} (depends on completion of previous goal) [Get Firefox on a Trajectory of Growth, Scale Firefox OS] - bare metal openstack is proving to be too bleeding edge and buggy to use for production services. We will continue to work on R&D for this project and track changes made in the openstack code base, but we will not move any services to production in FY2014 }}
** {{drop| Create self-service capability for releng hardware Firefox windows test slaves. {{bug|967064}} [Get Firefox on a Growth Trajectory] - Still pending completion of re-prioritized 2008R2 work }}

=== Developer Services ===
* {{new|(with B-team) roll out phase 2 of new review tooling}} [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{new|Upgrade existing Mercurial infrastructure to support more rapid, safe, and coordinated deployment of updates.}} [Get Firefox on a Growth Trajectory / Enable communities with impact]

[https://etherpad.mozilla.org/devservices-Q32014 Full List]

=== Security & Privacy Engineering ===
More details here: [[SecurityEngineering/2014/Q3Goals]]

'''Content Security'''
* {{ok|Gecko Security Hooks: Finish code and debugging for New Channel API, start getting reviews}} (dri=tanvi)
* {{ok|Gecko Security Hooks: Create plan for addon compatibility}} (dri=tanvi)
* {{done|CSP: Remove old JS implementation from mozilla-central}} (dri=sstamm)
* {{new|Evangelism: Security Open Mic presentation + blog post about new CSP implementation, maybe again as brown bag.}} (dri=sstamm)
* {{ok|''[stretch goal]'' CSP: Fix majority of CSP 1.1 compatibility bugs}} (dri=ckerschb)

'''Tracking Protection'''
* {{ok|Referer: Finish implementation of <meta> referrer control with volunteer help}} (dri=sstamm)
* {{done|Land first implementation of protection in Fx 33/34 off by default.}} (dri=mmc)

'''Communications Security'''
* {{ok|SSL Error Reporting finish first implementation of ssl error reporting feature.}} (dri=grobinson)
* {{ok| HPKP - implement pinning http header}} (dri=cviecco)
* {{new| Update roadmap for Cert Revocation improvements}} (dri=rbarnes)
* {{done| Create a mechanism to provision phones with an alternate cert}} (dri=mgoodwin)
* {{ok| Add measurement/enforcement of compliance with CABF Baseline Requirements}} (dri=keeler)
* {{ok| Create a tool for testing CA certificate compliance and EV-readiness}} (dri=keeler)
* {{ok| Add support for key wrap/unwrap and ECC in WebCrypto}} (dri=rbarnes)
* {{ok| ''[stretch goal]'' Get CA Program data into one database}} (dri=kathleen)

=== Firefox and Platform Security ===

* [https://mana.mozilla.org/wiki/display/~gkwong@mozilla.com/Marifuzz Marifuzz ] fuzzer ported to and running on Flame devices.
* Update ASan and LSan work for DOMFuzzer
* Update "Bounty Stars" document with issues found by external reporters and updating DOMFuzzer to reflect these results.
* Get Clang on RelEng ready for official OS X ASan builds.
* Initial work to move CoreFuzz towards running in cloud environments.
* WebCrypto API fuzzing using Dharma fuzzer.
* Port a portion of WebRTC fuzzing from Frambois fuzzer to Dharma fuzzer.
* Peach: Improving and porting Peach 2 to Python 3.
* Public Mozilla Security Github work: Moving of fuzzing tools from Fuzzing Hg to GitHub, including work to separate harnesses from testcase generation tools.

=== Games Program ===
*Reach out to 3rd party engines en masse (also for Q4)
*Select a 3D demo for mobile
*Pick a partner demo to optimize for mobile
*Focus on supporting shipping games and maintaining platform stability
*Focus on Shared Array Buffer implementation
*WebGL Benchmarks
*Continue to work MDN documentation; get Emscripten documentation started
*GDC and MWC event support plan

=== Release Management ===
For full list, see [[Release_Management/Goals/2014Q3#Release_Management_General|Release Management 2014Q3 Goals]].
* Create and document process for Desktop/Mobile feature fast tracking
* Determine future of ESR and how to manage this channel
* Continue desktop throttling experiment with intention of reducing throttled time while maintaining existing level of feedback
* Improve release notes with revamped template for all products
* Create B2G release model proposals and gather feedback for potential changes
* Figure out what to do with B2G Security Releases

===Program Management===

See this wiki page for a full list of [https://wiki.mozilla.org/Program_Management/Firefox/2014-Q3-Goals Program Management goals].

* Create a set of dashboards based on the ES database to track platform projects and surface bottlenecks.
* Brown bag presentation/restropective on the agile processes we are using on Desktop and FirefoxOS.
* Evaluate and produce a report on several tools for helping organize and visualize team backlogs and priority lists; wiki, spreadsheets, Trello, Kanbanize.

=== Quality Engineering ===
See this wiki for the full list of [https://wiki.mozilla.org/QA/Goals/2014q3 Quality goals]. What follows are our brief summary of our internal improvement goals for each strategic team.
* Firefox QA - Revitalize our Quality Engineering strategy by switching to a feature-based test strategy for all Firefox browser products so that there are test plans for each feature and testing is executed within two sprints of the feature's code landing
* Firefox OS - Better metrics for quality analysis, provide opportunities for community contribution, and expanding the role of our on-device automation for reporting to Treeherder.
* Services - Ensure new offerings have 98% uptime (FxA Sync, OAuth, FMD, Loop) and no more than 2 P1 bugs discovered post launch while building a core contributor base in services
* Marketplace - Ensure Marketplace's new payments backend, in-app payments, and the Marketplace feed land with high quality releases.
* Platform QA - Deploy into continuous integration a regression testing system for WebRTC along three areas of investigation: 1. "Smoke" tests, 2. Connection tests, and 3. Connection quality tests. These will be performed in a variety of environments, including various network topologies with various performance characteristics, connections between various versions of Firefox, and connections on multiple OS platforms. Test plans will be developed, and we will measure coverage of test plans. Results will be posted and available in Treeherder. We will also build backlog for next Platform Tiger Team tasks.
* Community - Increase conversion of interested and casual contributors to help them become active contributors with strong ties to the QA community

Platform/2014-Q3-Goals

2014-08-22T21:47:06Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
Items marked [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 here] with release 33 and 34 are part of the Q3 landings.

=== Layout ===
* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Enable Vertical Text for major use cases for Chinese & Japanese
** {{ok|bug 145503}}

* Text Performance
** {{ok|{{bug|998869}}}} Streamline parsing of fontlists and improve efficiency of font matching code (note: unicode-range support will fall out of this work)
** {{ok|{{bug|934770}}}} - slow at rendering large blocks of plain text
** {{ok|{{bug|860492}}}} - Divide large text runs into smaller runs to avoid chrome hangs

* Improve Restyling Performance
** {{ok|bug 977991}}

* {{ok|Font Inflation and Reflow-on-Zoom }}
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Projects with Adobe
** {{ok|CSS Filters}}

* Animations & Transitions
** {{ok|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{ok|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|TBD}}

* CSS Scrolling
** {{ok|CSS scroll snapping}}
** {{ok|scroll-behavior:smooth}}

* CSS Flexbox
** {{ok|performance bugs}}
** {{ok|spec changes}}

* CSS Ruby
** {{ok|implementation}}

=== Media ===
* {{ok|Enable MSE/VP9 for Firefox 33 in Nightly/Aurora}}
* {{ok|Enable MSE/MP4 on Windows and Firefox OS for Firefox 34}}

=== DOM ===
* {{ok|Mirror prototype of DOM objects through xray wrappers (peterv)}}
* {{ok|Remove nsDOMClassInfo.cpp}}
* {{done|Make less-privileged non-Xrayable unwaived opaque from privileged code (bholley, {{bug|856067}})}}
* {{done|Route all JSContext pushing through AutoJSAPI and Implement GetEntryGlobal (bobowen, bholley, {{bug|951991}})}}
* {{ok|Land <picture> preffed on on nightly ({{bug|1017875}}) (johns)}}
* {{ok|audit callsites of IsInDoc()/GetCurrentDoc to ensure correct Shadow DOM behaviour and fix Shadow DOM blockers for Gaia (smaug, wchen) ({{bug|1026047}})}}
* {{ok|land Service Workers preffed on on nightly (nsm, bkelly, baku) ({{bug|903441}})}}

=== WebAPI ===
* {{ok|create design plan for "share" activity (flow, what kind of objects are involved) (annevk)}}
* {{ok|document existing activities usage in gaia (ehsan)}}
* {{ok|get [https://w3c.github.io/screen-orientation/ screen orientation spec] to LC (marcosc)}}
* {{ok|publish use cases and spec for [http://w3c.github.io/screen-wake/ "wakelock" API] (marcosc)}}
* {{ok|24/12 hour format API (ehsan) {{bug|903683}}}}
* {{ok|{{bug|942542}} new quota API on PBackground for Service Worker cache (janv)}}
* {{ok|{{bug|701634}} IndexedDB in workers (bent)}}

=== JS ===
* {{jok|837314}} ES6 classes
* {{jok|941796}} Generational GC on Firefox OS
* {{jok|650161}} Compacting GC to reduce memory usage
* {{jok|856533}} Escape analysis JIT optimizations
* {{jok|998392}} Use Latin1 strings to reduce memory usage
* {{jok|903519}} Allocate strings in GC nursery (for performance)
* {{jok|972710}} ARM64 JIT ''[stretch goal]''

=== Accessibility ===
* {{ok|}}e10s: proxy the common a11y API stuff like name, role, and states.
* {{ok|}}GAIA: Fix [https://bugzilla.mozilla.org/buglist.cgi?priority=--&f1=blocked&list_id=10674217&o1=anyexact&resolution=---&query_based_on=b2ga11y%20p%3D1&o2=substring&query_format=advanced&f2=status_whiteboard&v1=893789&component=Disability%20Access%20APIs&component=Gaia&component=Gaia%3A%3ABluetooth%20File%20Transfer&component=Gaia%3A%3ABrowser&component=Gaia%3A%3ABuild&component=Gaia%3A%3ACalendar&component=Gaia%3A%3ACamera&component=Gaia%3A%3AClock&component=Gaia%3A%3AContacts&component=Gaia%3A%3ACost%20Control&component=Gaia%3A%3ADialer&component=Gaia%3A%3AE-Mail&component=Gaia%3A%3AEverything.me&component=Gaia%3A%3AFirst%20Time%20Experience&component=Gaia%3A%3AFMRadio&component=Gaia%3A%3AGallery&component=Gaia%3A%3AGithubBot&component=Gaia%3A%3AHomescreen&component=Gaia%3A%3AKeyboard&component=Gaia%3A%3AL10n&component=Gaia%3A%3ALoop&component=Gaia%3A%3AMusic&component=Gaia%3A%3ANotes&component=Gaia%3A%3APDF%20Viewer&component=Gaia%3A%3APerformanceTest&component=Gaia%3A%3ARingtones&component=Gaia%3A%3ASearch&component=Gaia%3A%3ASettings&component=Gaia%3A%3ASMS&component=Gaia%3A%3ASystem&component=Gaia%3A%3ASystem%3A%3ABrowser%20Chrome&component=Gaia%3A%3ASystem%3A%3AInput%20Mgmt&component=Gaia%3A%3ASystem%3A%3ALockscreen&component=Gaia%3A%3ASystem%3A%3AWindow%20Mgmt&component=Gaia%3A%3ATestAgent&component=Gaia%3A%3AUI%20Tests&component=Gaia%3A%3AVideo&component=Gaia%3A%3AWallpaper&component=Gaia%3A%3AWappush&v2=b2ga11y%20p%3D1&product=Core&product=Firefox%20OS all Gaia P1 a11y bugs] (~30 at this time).
* {{done|}}FFOS: {{Bug|1030465}} - Volume change should update the screen reader volume.
* {{done|}}FFOS: {{Bug|1030466}} - Headphones screen reader volume is too low.
* {{ok|}}FFOS: {{Bug|1030468}} - VC rectangle needs to work with scaled content.
* {{done|}}FFOS: {{Bug|1030470}} - Localization needs to work when switching locales in FxOS.

=== Perf ===

Fix major source of browser jank:

* {{ok|Initialize plugin instances asynchronously {{bug|998863}} }}
* {{ok|Pause heavy main-thread activities while user is interacting with the browser: }}
** {{ok|Determine when a user is actively interacting with the browser}}
** {{ok|Detect when jank occurs during interactions and report to Telemetry {{bug|1017055}} }}
** {{ok|Experiment with hinting to GC & CC that they should pause while the user is interacting with the browser}}
* {{ok|Help Frontend team with Places refactoring, eliminate some of the [http://telemetry.mozilla.org/slowsql/ Places main-thread SQL] reported to Telemetry }}
* {{ok|Don't store UI customization in localstore.rdf, use off-main thread JSON instead {{bug|559505}} }}

Improve Firefox startup (identified as a top issue in user research):

* {{ok|Reduce appearance of the "profile is in use" message on startup {{bug|286355}} }}
* {{ok|Restore windows one by one during session-restore {{bug|1034534}} and/or load windows by descending z-order {{bug|1034036}} }}
* {{ok|C++ version of AsyncShutdown {{bug|918317}} }}

Prevent performance regressions:

* {{ok|Implement automatic detection & alerting for Telemetry regressions {{bug|1031032}} }}
* {{ok|Help developers understand & diagnose Talos regressions}}, e.g. [https://bugzilla.mozilla.org/show_bug.cgi?id=1026550 Firefox 33 regression tracking], [https://bugzilla.mozilla.org/show_bug.cgi?id=1004427 Firefox 32 regressions], [https://bugzilla.mozilla.org/show_bug.cgi?id=990085 Firefox 31]

Grow community:

* {{ok|Mentor at least 5 external contributors}}

=== Networking ===

* {{ok|Ship Network Predictor ("Seer") on nightly, using HTTP cache instead of SQLite ({{bug|1009122}}) (hurley)}}
* {{ok|Ship current (hopefully final) IETF version of HTTP/2 preffed on in nightly (hurley)}}
* {{ok|HTTP/2 "alt-svc" support ({{bug|1003448}}) (mcmanus)}}
* {{ok|HTTP cache: determine if revalidation is needed w/o doing I/O ({{bug|983122}}) (sworkman) }}
* {{ok|Network up/down link detection on all platforms ({{bug|939318}}) (bagder) }}
* {{ok|Implement WebSocket compression extension ({{bug|792831}}) (michal) }}

=== Mobile ===

=== A*Team ===

For full list, see [[Auto-tools/Goals/2014Q3|A-Team Goals 2014Q3]]

'''B2G'''
* {{ok|}} Run a set of performance and correctness tests per-commit to b2g-inbound on Flame devices
* {{ok|}} Get gaia-integration tests running on device
* {{ok|}} Expand the FxOS Certification Suite with 1.4 support, test automation to prevent regressions, and investigation of support for non-phone devices
* {{ok|}} Green up B2G tests on TaskCluster (joint with RelEng)

'''Developer Productivity'''
* {{ok|}} Deploy ReviewBoard for developers to start using (joint with RelEng)

'''Performance'''
* {{ok|}} Deploy new Talos tests for tp5o_scroll, webgl, webrtc, and mainthread I/O
* {{ok|}} Get Datazilla alerts to beta mode (full parity with graph server alerts) with reduced noise
* {{ok|}} Get Eideticker running against Android again with increased frequency
* {{ok|}} Run B2G Eideticker against same branch/build combinations as our other on-device perf tests
* {{ok|}} Stand up a Games Benchmarking system for webaudio tests running against Firefox and Chrome

'''Treeherder'''
* {{ok|}} Deliver performance web service for ingesting and returning performance data
* {{ok|}} Deliver a UI for viewing Talos data

'''Sheriffing'''
* {{ok|}} Fully transition sheriffing from TBPL to Treeherder

'''General Automation'''
* {{ok|}} Create weekly reports that describe how many tests have been added/disabled/enabled per suite and platform
* {{ok|}} Move reftest to mozbase
* {{ok|}} Add command executors for Marionette for Java and Python

'''Bugzilla'''
* {{done|}} Improve load time of related bugs; can decrease show_bug load times by up to 12%
* {{ok|}} Minify and concatenate JS files
* {{ok|}} Authoritative view for review history
* {{ok|}} Rewrite docs for REST API

'''Community'''
* {{ok|}} Create good_next_bugs (name can be adjusted) so once contributors are comfortable they can do more serious coding/problem solving on a project they are familiar with
* {{ok|}} Monthly review of mentored bugs and projects

=== Web Engineering ===
'''Crash stats'''
* {{ok|}} Prototype service for identifying post-crash user actions
* {{ok|}} Hardware and performance tuning for new primary data store
* {{ok|}} Remove older, redundant crash storage format from database
* {{ok|}} Improve search performance and features
* {{ok|}} Replace interfaces to deprecated external data sources
* {{ok|}} Remove barriers to community installations
'''FHR'''
* {{ok|}} Support search diversion plan
'''DXR'''
* {{ok|}} Improve infrastructure.
** For example, switch to ES backend, which will enable us to build multi-language support and parallel tree indexing.
* {{ok|}} Broaden our audience.
** Pull users away from MXR so we can shut it off. For example, add support for Rust or JS, squash MXR migration blockers.
'''l10n'''
* {{ok|}} Get l10n build logs into a searchable data store
* {{ok|}} Replace some buildbot functionality with a10n automation
'''Air Mozilla'''
* {{ok|}} Prototype support for streaming media boxes
* {{ok|}} Improve desktop user experience

[https://etherpad.mozilla.org/webeng-q32014 full list]

=== SUMO and Input ===
* {{done|}} SUMO: Launch new offline SUMO app [Get Firefox on a Growth Trajectory]
* {{ok|}} SUMO: Develop new Community Hub to a level where it can replace legacy Karma app [Enable Communities with Impact]
* {{ok|}} SUMO: Research and prototype new experimental features (e.g. geotargeting, Instant Search, Search Suggestions) [Get Firefox on a Growth Trajectory]

* {{done|}} Input: Improve documentation and install to lower the bar for contribution [Enable Communities with Impact]
* {{ok|}} Input: Support Heartbeat [Get Firefox on a Growth Trajectory]
* {{ok|}} Input: Dashboards for Everyone [Get Firefox on a Growth Trajectory]

=== Release Engineering - Laura ===
* {{ok|}} Enable capacity expansion for bare-metal releng OS X build and test slaves via hardware provided by third-party datacenters (Get Firefox on a Trajectory of Growth)
* {{ok|}} Simplify release engineering mobile hardware infrastructure (Get Firefox on a Trajectory of Growth)
* {{ok|}} Automate developer access to continuous integration resources to expedite debugging and standing up new job variants. (Enable Communities With Impact)
* {{ok|}} Help enable video operability on the web by providing continuous integration for Cisco Open H.264 builds. (Get Firefox on a Trajectory of Growth)

=== Release Engineering - Taras ===
* {{ok|}} Replace aging Firefox update service with a scalable, modern solution. (Get Firefox on a Trajectory of Growth)
* {{ok|}} Simplify developer workflow by automating patch landing and uplift. (Enable Communities With Impact)
* {{ok|}} Optimize network transfers for build/test automation between datacenters. (Enable Communities With Impact)
* {{ok|}} Continue AWS cost optimizations: EBS < 3% of AWS bill(vs 30% in Q2) (Enable Communities With Impact)
* {{ok|}} Improve developer workflow by migrating 80% of FirefoxOS build/test jobs to taskcluster (Enable Communities With Impact)
* {{ok|}} Turn telemetry is into a general purpose s3 ingester and analysis tool

=== Release Engineering Operations ===
* Build/Test System Performance Enhancements
** {{risk| Unify releng platform architecture, using common tools and best practices, to decrease complexity and enable smoother developer engagement {{bug|1026110}} [Get Firefox on a Trajectory of Growth, Enable Communities With Impact] - blocked on obtaining resources from other groups }}
** {{ok| Improve communication and response time for releng network flow requests {{bug|1026112}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{ok| Improve security for all releng windows infrastructure {{bug|893716}} [Get Firefox on a Trajectory of Growth] }}
** {{done| Update windows platform developer tools {{bug|1019165}} [Get Firefox on a Trajectory of Growth] }}
* Build/Test System Self-Serve Re-architecture
** {{prev| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{drop| Create self-service capability for releng hardware Firefox linux test slaves (build slaves as a stretch goal) {{bug|1026687}} (depends on completion of previous goal) [Get Firefox on a Trajectory of Growth, Scale Firefox OS] - bare metal openstack is proving to be too bleeding edge and buggy to use for production services. We will continue to work on this project and track changes made in the opernstack code base, but we will not move any services to production }}
** {{drop| Create self-service capability for releng hardware Firefox windows test slaves. {{bug|967064}} [Get Firefox on a Growth Trajectory] - Still pending completion of re-prioritized 2008R2 work }}

=== Developer Services ===
* {{new|(with B-team) roll out phase 2 of new review tooling}} [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{new|Upgrade existing Mercurial infrastructure to support more rapid, safe, and coordinated deployment of updates.}} [Get Firefox on a Growth Trajectory / Enable communities with impact]

[https://etherpad.mozilla.org/devservices-Q32014 Full List]

=== Security & Privacy Engineering ===
More details here: [[SecurityEngineering/2014/Q3Goals]]

'''Content Security'''
* {{ok|Gecko Security Hooks: Finish code and debugging for New Channel API, start getting reviews}} (dri=tanvi)
* {{ok|Gecko Security Hooks: Create plan for addon compatibility}} (dri=tanvi)
* {{done|CSP: Remove old JS implementation from mozilla-central}} (dri=sstamm)
* {{new|Evangelism: Security Open Mic presentation + blog post about new CSP implementation, maybe again as brown bag.}} (dri=sstamm)
* {{ok|''[stretch goal]'' CSP: Fix majority of CSP 1.1 compatibility bugs}} (dri=ckerschb)

'''Tracking Protection'''
* {{ok|Referer: Finish implementation of <meta> referrer control with volunteer help}} (dri=sstamm)
* {{done|Land first implementation of protection in Fx 33/34 off by default.}} (dri=mmc)

'''Communications Security'''
* {{ok|SSL Error Reporting finish first implementation of ssl error reporting feature.}} (dri=grobinson)
* {{ok| HPKP - implement pinning http header}} (dri=cviecco)
* {{new| Update roadmap for Cert Revocation improvements}} (dri=rbarnes)
* {{done| Create a mechanism to provision phones with an alternate cert}} (dri=mgoodwin)
* {{ok| Add measurement/enforcement of compliance with CABF Baseline Requirements}} (dri=keeler)
* {{ok| Create a tool for testing CA certificate compliance and EV-readiness}} (dri=keeler)
* {{ok| Add support for key wrap/unwrap and ECC in WebCrypto}} (dri=rbarnes)
* {{ok| ''[stretch goal]'' Get CA Program data into one database}} (dri=kathleen)

=== Firefox and Platform Security ===

* [https://mana.mozilla.org/wiki/display/~gkwong@mozilla.com/Marifuzz Marifuzz ] fuzzer ported to and running on Flame devices.
* Update ASan and LSan work for DOMFuzzer
* Update "Bounty Stars" document with issues found by external reporters and updating DOMFuzzer to reflect these results.
* Get Clang on RelEng ready for official OS X ASan builds.
* Initial work to move CoreFuzz towards running in cloud environments.
* WebCrypto API fuzzing using Dharma fuzzer.
* Port a portion of WebRTC fuzzing from Frambois fuzzer to Dharma fuzzer.
* Peach: Improving and porting Peach 2 to Python 3.
* Public Mozilla Security Github work: Moving of fuzzing tools from Fuzzing Hg to GitHub, including work to separate harnesses from testcase generation tools.

=== Games Program ===
*Reach out to 3rd party engines en masse (also for Q4)
*Select a 3D demo for mobile
*Pick a partner demo to optimize for mobile
*Focus on supporting shipping games and maintaining platform stability
*Focus on Shared Array Buffer implementation
*WebGL Benchmarks
*Continue to work MDN documentation; get Emscripten documentation started
*GDC and MWC event support plan

=== Release Management ===
For full list, see [[Release_Management/Goals/2014Q3#Release_Management_General|Release Management 2014Q3 Goals]].
* Create and document process for Desktop/Mobile feature fast tracking
* Determine future of ESR and how to manage this channel
* Continue desktop throttling experiment with intention of reducing throttled time while maintaining existing level of feedback
* Improve release notes with revamped template for all products
* Create B2G release model proposals and gather feedback for potential changes
* Figure out what to do with B2G Security Releases

===Program Management===

See this wiki page for a full list of [https://wiki.mozilla.org/Program_Management/Firefox/2014-Q3-Goals Program Management goals].

* Create a set of dashboards based on the ES database to track platform projects and surface bottlenecks.
* Brown bag presentation/restropective on the agile processes we are using on Desktop and FirefoxOS.
* Evaluate and produce a report on several tools for helping organize and visualize team backlogs and priority lists; wiki, spreadsheets, Trello, Kanbanize.

=== Quality Engineering ===
See this wiki for the full list of [https://wiki.mozilla.org/QA/Goals/2014q3 Quality goals]. What follows are our brief summary of our internal improvement goals for each strategic team.
* Firefox QA - Revitalize our Quality Engineering strategy by switching to a feature-based test strategy for all Firefox browser products so that there are test plans for each feature and testing is executed within two sprints of the feature's code landing
* Firefox OS - Better metrics for quality analysis, provide opportunities for community contribution, and expanding the role of our on-device automation for reporting to Treeherder.
* Services - Ensure new offerings have 98% uptime (FxA Sync, OAuth, FMD, Loop) and no more than 2 P1 bugs discovered post launch while building a core contributor base in services
* Marketplace - Ensure Marketplace's new payments backend, in-app payments, and the Marketplace feed land with high quality releases.
* Platform QA - Deploy into continuous integration a regression testing system for WebRTC along three areas of investigation: 1. "Smoke" tests, 2. Connection tests, and 3. Connection quality tests. These will be performed in a variety of environments, including various network topologies with various performance characteristics, connections between various versions of Firefox, and connections on multiple OS platforms. Test plans will be developed, and we will measure coverage of test plans. Results will be posted and available in Treeherder. We will also build backlog for next Platform Tiger Team tasks.
* Community - Increase conversion of interested and casual contributors to help them become active contributors with strong ties to the QA community

Platform/2014-Q3-Goals

2014-08-22T20:12:50Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
Items marked [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 here] with release 33 and 34 are part of the Q3 landings.

=== Layout ===
* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Enable Vertical Text for major use cases for Chinese & Japanese
** {{ok|bug 145503}}

* Text Performance
** {{ok|{{bug|998869}}}} Streamline parsing of fontlists and improve efficiency of font matching code (note: unicode-range support will fall out of this work)
** {{ok|{{bug|934770}}}} - slow at rendering large blocks of plain text
** {{ok|{{bug|860492}}}} - Divide large text runs into smaller runs to avoid chrome hangs

* Improve Restyling Performance
** {{ok|bug 977991}}

* {{ok|Font Inflation and Reflow-on-Zoom }}
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Projects with Adobe
** {{ok|CSS Filters}}

* Animations & Transitions
** {{ok|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{ok|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|TBD}}

* CSS Scrolling
** {{ok|CSS scroll snapping}}
** {{ok|scroll-behavior:smooth}}

* CSS Flexbox
** {{ok|performance bugs}}
** {{ok|spec changes}}

* CSS Ruby
** {{ok|implementation}}

=== Media ===
* {{ok|Enable MSE/VP9 for Firefox 33 in Nightly/Aurora}}
* {{ok|Enable MSE/MP4 on Windows and Firefox OS for Firefox 34}}

=== DOM ===
* {{ok|Mirror prototype of DOM objects through xray wrappers (peterv)}}
* {{ok|Remove nsDOMClassInfo.cpp}}
* {{done|Make less-privileged non-Xrayable unwaived opaque from privileged code (bholley, {{bug|856067}})}}
* {{done|Route all JSContext pushing through AutoJSAPI and Implement GetEntryGlobal (bobowen, bholley, {{bug|951991}})}}
* {{ok|Land <picture> preffed on on nightly ({{bug|1017875}}) (johns)}}
* {{ok|audit callsites of IsInDoc()/GetCurrentDoc to ensure correct Shadow DOM behaviour and fix Shadow DOM blockers for Gaia (smaug, wchen) ({{bug|1026047}})}}
* {{ok|land Service Workers preffed on on nightly (nsm, bkelly, baku) ({{bug|903441}})}}

=== WebAPI ===
* {{ok|create design plan for "share" activity (flow, what kind of objects are involved) (annevk)}}
* {{ok|document existing activities usage in gaia (ehsan)}}
* {{ok|get [https://w3c.github.io/screen-orientation/ screen orientation spec] to LC (marcosc)}}
* {{ok|publish use cases and spec for [http://w3c.github.io/screen-wake/ "wakelock" API] (marcosc)}}
* {{ok|24/12 hour format API (ehsan) {{bug|903683}}}}
* {{ok|{{bug|942542}} new quota API on PBackground for Service Worker cache (janv)}}
* {{ok|{{bug|701634}} IndexedDB in workers (bent)}}

=== JS ===
* {{jok|837314}} ES6 classes
* {{jok|941796}} Generational GC on Firefox OS
* {{jok|650161}} Compacting GC to reduce memory usage
* {{jok|856533}} Escape analysis JIT optimizations
* {{jok|998392}} Use Latin1 strings to reduce memory usage
* {{jok|903519}} Allocate strings in GC nursery (for performance)
* {{jok|972710}} ARM64 JIT ''[stretch goal]''

=== Accessibility ===
* {{ok|}}e10s: proxy the common a11y API stuff like name, role, and states.
* {{ok|}}GAIA: Fix [https://bugzilla.mozilla.org/buglist.cgi?priority=--&f1=blocked&list_id=10674217&o1=anyexact&resolution=---&query_based_on=b2ga11y%20p%3D1&o2=substring&query_format=advanced&f2=status_whiteboard&v1=893789&component=Disability%20Access%20APIs&component=Gaia&component=Gaia%3A%3ABluetooth%20File%20Transfer&component=Gaia%3A%3ABrowser&component=Gaia%3A%3ABuild&component=Gaia%3A%3ACalendar&component=Gaia%3A%3ACamera&component=Gaia%3A%3AClock&component=Gaia%3A%3AContacts&component=Gaia%3A%3ACost%20Control&component=Gaia%3A%3ADialer&component=Gaia%3A%3AE-Mail&component=Gaia%3A%3AEverything.me&component=Gaia%3A%3AFirst%20Time%20Experience&component=Gaia%3A%3AFMRadio&component=Gaia%3A%3AGallery&component=Gaia%3A%3AGithubBot&component=Gaia%3A%3AHomescreen&component=Gaia%3A%3AKeyboard&component=Gaia%3A%3AL10n&component=Gaia%3A%3ALoop&component=Gaia%3A%3AMusic&component=Gaia%3A%3ANotes&component=Gaia%3A%3APDF%20Viewer&component=Gaia%3A%3APerformanceTest&component=Gaia%3A%3ARingtones&component=Gaia%3A%3ASearch&component=Gaia%3A%3ASettings&component=Gaia%3A%3ASMS&component=Gaia%3A%3ASystem&component=Gaia%3A%3ASystem%3A%3ABrowser%20Chrome&component=Gaia%3A%3ASystem%3A%3AInput%20Mgmt&component=Gaia%3A%3ASystem%3A%3ALockscreen&component=Gaia%3A%3ASystem%3A%3AWindow%20Mgmt&component=Gaia%3A%3ATestAgent&component=Gaia%3A%3AUI%20Tests&component=Gaia%3A%3AVideo&component=Gaia%3A%3AWallpaper&component=Gaia%3A%3AWappush&v2=b2ga11y%20p%3D1&product=Core&product=Firefox%20OS all Gaia P1 a11y bugs] (~30 at this time).
* {{done|}}FFOS: {{Bug|1030465}} - Volume change should update the screen reader volume.
* {{done|}}FFOS: {{Bug|1030466}} - Headphones screen reader volume is too low.
* {{ok|}}FFOS: {{Bug|1030468}} - VC rectangle needs to work with scaled content.
* {{done|}}FFOS: {{Bug|1030470}} - Localization needs to work when switching locales in FxOS.

=== Perf ===

Fix major source of browser jank:

* {{ok|Initialize plugin instances asynchronously {{bug|998863}} }}
* {{ok|Pause heavy main-thread activities while user is interacting with the browser: }}
** {{ok|Determine when a user is actively interacting with the browser}}
** {{ok|Detect when jank occurs during interactions and report to Telemetry {{bug|1017055}} }}
** {{ok|Experiment with hinting to GC & CC that they should pause while the user is interacting with the browser}}
* {{ok|Help Frontend team with Places refactoring, eliminate some of the [http://telemetry.mozilla.org/slowsql/ Places main-thread SQL] reported to Telemetry }}
* {{ok|Don't store UI customization in localstore.rdf, use off-main thread JSON instead {{bug|559505}} }}

Improve Firefox startup (identified as a top issue in user research):

* {{ok|Reduce appearance of the "profile is in use" message on startup {{bug|286355}} }}
* {{ok|Restore windows one by one during session-restore {{bug|1034534}} and/or load windows by descending z-order {{bug|1034036}} }}
* {{ok|C++ version of AsyncShutdown {{bug|918317}} }}

Prevent performance regressions:

* {{ok|Implement automatic detection & alerting for Telemetry regressions {{bug|1031032}} }}
* {{ok|Help developers understand & diagnose Talos regressions}}, e.g. [https://bugzilla.mozilla.org/show_bug.cgi?id=1026550 Firefox 33 regression tracking], [https://bugzilla.mozilla.org/show_bug.cgi?id=1004427 Firefox 32 regressions], [https://bugzilla.mozilla.org/show_bug.cgi?id=990085 Firefox 31]

Grow community:

* {{ok|Mentor at least 5 external contributors}}

=== Networking ===

* {{ok|Ship Network Predictor ("Seer") on nightly, using HTTP cache instead of SQLite ({{bug|1009122}}) (hurley)}}
* {{ok|Ship current (hopefully final) IETF version of HTTP/2 preffed on in nightly (hurley)}}
* {{ok|HTTP/2 "alt-svc" support ({{bug|1003448}}) (mcmanus)}}
* {{ok|HTTP cache: determine if revalidation is needed w/o doing I/O ({{bug|983122}}) (sworkman) }}
* {{ok|Network up/down link detection on all platforms ({{bug|939318}}) (bagder) }}
* {{ok|Implement WebSocket compression extension ({{bug|792831}}) (michal) }}

=== Mobile ===

=== A*Team ===

For full list, see [[Auto-tools/Goals/2014Q3|A-Team Goals 2014Q3]]

'''B2G'''
* {{ok|}} Run a set of performance and correctness tests per-commit to b2g-inbound on Flame devices
* {{ok|}} Get gaia-integration tests running on device
* {{ok|}} Expand the FxOS Certification Suite with 1.4 support, test automation to prevent regressions, and investigation of support for non-phone devices
* {{ok|}} Green up B2G tests on TaskCluster (joint with RelEng)

'''Developer Productivity'''
* {{ok|}} Deploy ReviewBoard for developers to start using (joint with RelEng)

'''Performance'''
* {{ok|}} Deploy new Talos tests for tp5o_scroll, webgl, webrtc, and mainthread I/O
* {{ok|}} Get Datazilla alerts to beta mode (full parity with graph server alerts) with reduced noise
* {{ok|}} Get Eideticker running against Android again with increased frequency
* {{ok|}} Run B2G Eideticker against same branch/build combinations as our other on-device perf tests
* {{ok|}} Stand up a Games Benchmarking system for webaudio tests running against Firefox and Chrome

'''Treeherder'''
* {{ok|}} Deliver performance web service for ingesting and returning performance data
* {{ok|}} Deliver a UI for viewing Talos data

'''Sheriffing'''
* {{ok|}} Fully transition sheriffing from TBPL to Treeherder

'''General Automation'''
* {{ok|}} Create weekly reports that describe how many tests have been added/disabled/enabled per suite and platform
* {{ok|}} Move reftest to mozbase
* {{ok|}} Add command executors for Marionette for Java and Python

'''Bugzilla'''
* {{done|}} Improve load time of related bugs; can decrease show_bug load times by up to 12%
* {{ok|}} Minify and concatenate JS files
* {{ok|}} Authoritative view for review history
* {{ok|}} Rewrite docs for REST API

'''Community'''
* {{ok|}} Create good_next_bugs (name can be adjusted) so once contributors are comfortable they can do more serious coding/problem solving on a project they are familiar with
* {{ok|}} Monthly review of mentored bugs and projects

=== Web Engineering ===
'''Crash stats'''
* {{ok|}} Prototype service for identifying post-crash user actions
* {{ok|}} Hardware and performance tuning for new primary data store
* {{ok|}} Remove older, redundant crash storage format from database
* {{ok|}} Improve search performance and features
* {{ok|}} Replace interfaces to deprecated external data sources
* {{ok|}} Remove barriers to community installations
'''FHR'''
* {{ok|}} Support search diversion plan
'''DXR'''
* {{ok|}} Improve infrastructure.
** For example, switch to ES backend, which will enable us to build multi-language support and parallel tree indexing.
* {{ok|}} Broaden our audience.
** Pull users away from MXR so we can shut it off. For example, add support for Rust or JS, squash MXR migration blockers.
'''l10n'''
* {{ok|}} Get l10n build logs into a searchable data store
* {{ok|}} Replace some buildbot functionality with a10n automation
'''Air Mozilla'''
* {{ok|}} Prototype support for streaming media boxes
* {{ok|}} Improve desktop user experience

[https://etherpad.mozilla.org/webeng-q32014 full list]

=== SUMO and Input ===
* {{done|}} SUMO: Launch new offline SUMO app [Get Firefox on a Growth Trajectory]
* {{ok|}} SUMO: Develop new Community Hub to a level where it can replace legacy Karma app [Enable Communities with Impact]
* {{ok|}} SUMO: Research and prototype new experimental features (e.g. geotargeting, Instant Search, Search Suggestions) [Get Firefox on a Growth Trajectory]

* {{done|}} Input: Improve documentation and install to lower the bar for contribution [Enable Communities with Impact]
* {{ok|}} Input: Support Heartbeat [Get Firefox on a Growth Trajectory]
* {{ok|}} Input: Dashboards for Everyone [Get Firefox on a Growth Trajectory]

=== Release Engineering - Laura ===
* {{ok|}} Enable capacity expansion for bare-metal releng OS X build and test slaves via hardware provided by third-party datacenters (Get Firefox on a Trajectory of Growth)
* {{ok|}} Simplify release engineering mobile hardware infrastructure (Get Firefox on a Trajectory of Growth)
* {{ok|}} Automate developer access to continuous integration resources to expedite debugging and standing up new job variants. (Enable Communities With Impact)
* {{ok|}} Help enable video operability on the web by providing continuous integration for Cisco Open H.264 builds. (Get Firefox on a Trajectory of Growth)

=== Release Engineering - Taras ===
* {{ok|}} Replace aging Firefox update service with a scalable, modern solution. (Get Firefox on a Trajectory of Growth)
* {{ok|}} Simplify developer workflow by automating patch landing and uplift. (Enable Communities With Impact)
* {{ok|}} Optimize network transfers for build/test automation between datacenters. (Enable Communities With Impact)
* {{ok|}} Continue AWS cost optimizations: EBS < 3% of AWS bill(vs 30% in Q2) (Enable Communities With Impact)
* {{ok|}} Improve developer workflow by migrating 80% of FirefoxOS build/test jobs to taskcluster (Enable Communities With Impact)
* {{ok|}} Turn telemetry is into a general purpose s3 ingester and analysis tool

=== Release Engineering Operations ===
* Build/Test System Performance Enhancements
** {{ok| Unify releng platform architecture, using common tools and best practices, to decrease complexity and enable smoother developer engagement {{bug|1026110}} [Get Firefox on a Trajectory of Growth, Enable Communities With Impact] }}
** {{ok| Improve communication and response time for releng network flow requests {{bug|1026112}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{ok| Improve security for all releng windows infrastructure {{bug|893716}} [Get Firefox on a Trajectory of Growth] }}
** {{done| Update windows platform developer tools {{bug|1019165}} [Get Firefox on a Trajectory of Growth] }}
* Build/Test System Self-Serve Re-architecture
** {{prev| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{drop| Create self-service capability for releng hardware Firefox linux test slaves (build slaves as a stretch goal) {{bug|1026687}} (depends on completion of previous goal) [Get Firefox on a Trajectory of Growth, Scale Firefox OS] - bare metal openstack is proving to be too bleeding edge and buggy to use for production services. We will continue to work on this project and track changes made in the opernstack code base, but we will not move any services to production }}
** {{drop| Create self-service capability for releng hardware Firefox windows test slaves. {{bug|967064}} [Get Firefox on a Growth Trajectory] - Still pending completion of re-prioritized 2008R2 work }}

=== Developer Services ===
* {{new|(with B-team) roll out phase 2 of new review tooling}} [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{new|Upgrade existing Mercurial infrastructure to support more rapid, safe, and coordinated deployment of updates.}} [Get Firefox on a Growth Trajectory / Enable communities with impact]

[https://etherpad.mozilla.org/devservices-Q32014 Full List]

=== Security & Privacy Engineering ===
More details here: [[SecurityEngineering/2014/Q3Goals]]

'''Content Security'''
* {{ok|Gecko Security Hooks: Finish code and debugging for New Channel API, start getting reviews}} (dri=tanvi)
* {{ok|Gecko Security Hooks: Create plan for addon compatibility}} (dri=tanvi)
* {{done|CSP: Remove old JS implementation from mozilla-central}} (dri=sstamm)
* {{new|Evangelism: Security Open Mic presentation + blog post about new CSP implementation, maybe again as brown bag.}} (dri=sstamm)
* {{ok|''[stretch goal]'' CSP: Fix majority of CSP 1.1 compatibility bugs}} (dri=ckerschb)

'''Tracking Protection'''
* {{ok|Referer: Finish implementation of <meta> referrer control with volunteer help}} (dri=sstamm)
* {{done|Land first implementation of protection in Fx 33/34 off by default.}} (dri=mmc)

'''Communications Security'''
* {{ok|SSL Error Reporting finish first implementation of ssl error reporting feature.}} (dri=grobinson)
* {{ok| HPKP - implement pinning http header}} (dri=cviecco)
* {{new| Update roadmap for Cert Revocation improvements}} (dri=rbarnes)
* {{done| Create a mechanism to provision phones with an alternate cert}} (dri=mgoodwin)
* {{ok| Add measurement/enforcement of compliance with CABF Baseline Requirements}} (dri=keeler)
* {{ok| Create a tool for testing CA certificate compliance and EV-readiness}} (dri=keeler)
* {{ok| Add support for key wrap/unwrap and ECC in WebCrypto}} (dri=rbarnes)
* {{ok| ''[stretch goal]'' Get CA Program data into one database}} (dri=kathleen)

=== Firefox and Platform Security ===

* [https://mana.mozilla.org/wiki/display/~gkwong@mozilla.com/Marifuzz Marifuzz ] fuzzer ported to and running on Flame devices.
* Update ASan and LSan work for DOMFuzzer
* Update "Bounty Stars" document with issues found by external reporters and updating DOMFuzzer to reflect these results.
* Get Clang on RelEng ready for official OS X ASan builds.
* Initial work to move CoreFuzz towards running in cloud environments.
* WebCrypto API fuzzing using Dharma fuzzer.
* Port a portion of WebRTC fuzzing from Frambois fuzzer to Dharma fuzzer.
* Peach: Improving and porting Peach 2 to Python 3.
* Public Mozilla Security Github work: Moving of fuzzing tools from Fuzzing Hg to GitHub, including work to separate harnesses from testcase generation tools.

=== Games Program ===
*Reach out to 3rd party engines en masse (also for Q4)
*Select a 3D demo for mobile
*Pick a partner demo to optimize for mobile
*Focus on supporting shipping games and maintaining platform stability
*Focus on Shared Array Buffer implementation
*WebGL Benchmarks
*Continue to work MDN documentation; get Emscripten documentation started
*GDC and MWC event support plan

=== Release Management ===
For full list, see [[Release_Management/Goals/2014Q3#Release_Management_General|Release Management 2014Q3 Goals]].
* Create and document process for Desktop/Mobile feature fast tracking
* Determine future of ESR and how to manage this channel
* Continue desktop throttling experiment with intention of reducing throttled time while maintaining existing level of feedback
* Improve release notes with revamped template for all products
* Create B2G release model proposals and gather feedback for potential changes
* Figure out what to do with B2G Security Releases

===Program Management===

See this wiki page for a full list of [https://wiki.mozilla.org/Program_Management/Firefox/2014-Q3-Goals Program Management goals].

* Create a set of dashboards based on the ES database to track platform projects and surface bottlenecks.
* Brown bag presentation/restropective on the agile processes we are using on Desktop and FirefoxOS.
* Evaluate and produce a report on several tools for helping organize and visualize team backlogs and priority lists; wiki, spreadsheets, Trello, Kanbanize.

=== Quality Engineering ===
See this wiki for the full list of [https://wiki.mozilla.org/QA/Goals/2014q3 Quality goals]. What follows are our brief summary of our internal improvement goals for each strategic team.
* Firefox QA - Revitalize our Quality Engineering strategy by switching to a feature-based test strategy for all Firefox browser products so that there are test plans for each feature and testing is executed within two sprints of the feature's code landing
* Firefox OS - Better metrics for quality analysis, provide opportunities for community contribution, and expanding the role of our on-device automation for reporting to Treeherder.
* Services - Ensure new offerings have 98% uptime (FxA Sync, OAuth, FMD, Loop) and no more than 2 P1 bugs discovered post launch while building a core contributor base in services
* Marketplace - Ensure Marketplace's new payments backend, in-app payments, and the Marketplace feed land with high quality releases.
* Platform QA - Deploy into continuous integration a regression testing system for WebRTC along three areas of investigation: 1. "Smoke" tests, 2. Connection tests, and 3. Connection quality tests. These will be performed in a variety of environments, including various network topologies with various performance characteristics, connections between various versions of Firefox, and connections on multiple OS platforms. Test plans will be developed, and we will measure coverage of test plans. Results will be posted and available in Treeherder. We will also build backlog for next Platform Tiger Team tasks.
* Community - Increase conversion of interested and casual contributors to help them become active contributors with strong ties to the QA community

Platform/2014-Q3-Goals

2014-08-19T13:42:32Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
Items marked [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 here] with release 33 and 34 are part of the Q3 landings.

=== Layout ===
* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Enable Vertical Text for major use cases for Chinese & Japanese
** {{ok|bug 145503}}

* Text Performance
** {{ok|{{bug|998869}}}} Streamline parsing of fontlists and improve efficiency of font matching code (note: unicode-range support will fall out of this work)
** {{ok|{{bug|934770}}}} - slow at rendering large blocks of plain text
** {{ok|{{bug|860492}}}} - Divide large text runs into smaller runs to avoid chrome hangs

* Improve Restyling Performance
** {{ok|bug 977991}}

* {{ok|Font Inflation and Reflow-on-Zoom }}
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Projects with Adobe
** {{ok|CSS Filters}}

* Animations & Transitions
** {{ok|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{ok|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|TBD}}

* CSS Scrolling
** {{ok|CSS scroll snapping}}
** {{ok|scroll-behavior:smooth}}

* CSS Flexbox
** {{ok|performance bugs}}
** {{ok|spec changes}}

* CSS Ruby
** {{ok|implementation}}

=== Media ===
* {{ok|Enable MSE/VP9 for Firefox 33 in Nightly/Aurora}}
* {{ok|Enable MSE/MP4 on Windows and Firefox OS for Firefox 34}}

=== DOM ===
* {{ok|Mirror prototype of DOM objects through xray wrappers (peterv)}}
* {{ok|Remove nsDOMClassInfo.cpp}}
* {{done|Make less-privileged non-Xrayable unwaived opaque from privileged code (bholley, {{bug|856067}})}}
* {{ok|Route all JSContext pushing through AutoJSAPI and Implement GetEntryGlobal (bobowen, bholley, {{bug|951991}})}}
* {{ok|Land <picture> preffed on on nightly ({{bug|1017875}}) (johns)}}
* {{ok|audit callsites of IsInDoc()/GetCurrentDoc to ensure correct Shadow DOM behaviour and fix Shadow DOM blockers for Gaia (smaug, wchen) ({{bug|1026047}})}}
* {{ok|land Service Workers preffed on on nightly (nsm, bkelly, baku) ({{bug|903441}})}}

=== WebAPI ===
* {{ok|create design plan for "share" activity (flow, what kind of objects are involved) (annevk)}}
* {{ok|document existing activities usage in gaia (ehsan)}}
* {{ok|get [https://w3c.github.io/screen-orientation/ screen orientation spec] to LC (marcosc)}}
* {{ok|publish use cases and spec for [http://w3c.github.io/screen-wake/ "wakelock" API] (marcosc)}}
* {{ok|24/12 hour format API (ehsan) {{bug|903683}}}}
* {{ok|{{bug|942542}} new quota API on PBackground for Service Worker cache (janv)}}
* {{ok|{{bug|701634}} IndexedDB in workers (bent)}}

=== JS ===
* {{jok|837314}} ES6 classes
* {{jok|941796}} Generational GC on Firefox OS
* {{jok|650161}} Compacting GC to reduce memory usage
* {{jok|856533}} Escape analysis JIT optimizations
* {{jok|998392}} Use Latin1 strings to reduce memory usage
* {{jok|903519}} Allocate strings in GC nursery (for performance)
* {{jok|972710}} ARM64 JIT ''[stretch goal]''

=== Accessibility ===
* {{ok|}}e10s: proxy the common a11y API stuff like name, role, and states.
* {{ok|}}GAIA: Fix [https://bugzilla.mozilla.org/buglist.cgi?priority=--&f1=blocked&list_id=10674217&o1=anyexact&resolution=---&query_based_on=b2ga11y%20p%3D1&o2=substring&query_format=advanced&f2=status_whiteboard&v1=893789&component=Disability%20Access%20APIs&component=Gaia&component=Gaia%3A%3ABluetooth%20File%20Transfer&component=Gaia%3A%3ABrowser&component=Gaia%3A%3ABuild&component=Gaia%3A%3ACalendar&component=Gaia%3A%3ACamera&component=Gaia%3A%3AClock&component=Gaia%3A%3AContacts&component=Gaia%3A%3ACost%20Control&component=Gaia%3A%3ADialer&component=Gaia%3A%3AE-Mail&component=Gaia%3A%3AEverything.me&component=Gaia%3A%3AFirst%20Time%20Experience&component=Gaia%3A%3AFMRadio&component=Gaia%3A%3AGallery&component=Gaia%3A%3AGithubBot&component=Gaia%3A%3AHomescreen&component=Gaia%3A%3AKeyboard&component=Gaia%3A%3AL10n&component=Gaia%3A%3ALoop&component=Gaia%3A%3AMusic&component=Gaia%3A%3ANotes&component=Gaia%3A%3APDF%20Viewer&component=Gaia%3A%3APerformanceTest&component=Gaia%3A%3ARingtones&component=Gaia%3A%3ASearch&component=Gaia%3A%3ASettings&component=Gaia%3A%3ASMS&component=Gaia%3A%3ASystem&component=Gaia%3A%3ASystem%3A%3ABrowser%20Chrome&component=Gaia%3A%3ASystem%3A%3AInput%20Mgmt&component=Gaia%3A%3ASystem%3A%3ALockscreen&component=Gaia%3A%3ASystem%3A%3AWindow%20Mgmt&component=Gaia%3A%3ATestAgent&component=Gaia%3A%3AUI%20Tests&component=Gaia%3A%3AVideo&component=Gaia%3A%3AWallpaper&component=Gaia%3A%3AWappush&v2=b2ga11y%20p%3D1&product=Core&product=Firefox%20OS all Gaia P1 a11y bugs] (~30 at this time).
* {{done|}}FFOS: {{Bug|1030465}} - Volume change should update the screen reader volume.
* {{done|}}FFOS: {{Bug|1030466}} - Headphones screen reader volume is too low.
* {{ok|}}FFOS: {{Bug|1030468}} - VC rectangle needs to work with scaled content.
* {{done|}}FFOS: {{Bug|1030470}} - Localization needs to work when switching locales in FxOS.

=== Perf ===

Fix major source of browser jank:

* {{ok|Initialize plugin instances asynchronously {{bug|998863}} }}
* {{ok|Pause heavy main-thread activities while user is interacting with the browser: }}
** {{ok|Determine when a user is actively interacting with the browser}}
** {{ok|Detect when jank occurs during interactions and report to Telemetry {{bug|1017055}} }}
** {{ok|Experiment with hinting to GC & CC that they should pause while the user is interacting with the browser}}
* {{ok|Help Frontend team with Places refactoring, eliminate some of the [http://telemetry.mozilla.org/slowsql/ Places main-thread SQL] reported to Telemetry }}
* {{ok|Don't store UI customization in localstore.rdf, use off-main thread JSON instead {{bug|559505}} }}

Improve Firefox startup (identified as a top issue in user research):

* {{ok|Reduce appearance of the "profile is in use" message on startup {{bug|286355}} }}
* {{ok|Restore windows one by one during session-restore {{bug|1034534}} and/or load windows by descending z-order {{bug|1034036}} }}
* {{ok|C++ version of AsyncShutdown {{bug|918317}} }}

Prevent performance regressions:

* {{ok|Implement automatic detection & alerting for Telemetry regressions {{bug|1031032}} }}
* {{ok|Help developers understand & diagnose Talos regressions}}, e.g. [https://bugzilla.mozilla.org/show_bug.cgi?id=1026550 Firefox 33 regression tracking], [https://bugzilla.mozilla.org/show_bug.cgi?id=1004427 Firefox 32 regressions], [https://bugzilla.mozilla.org/show_bug.cgi?id=990085 Firefox 31]

Grow community:

* {{ok|Mentor at least 5 external contributors}}

=== Networking ===

* {{ok|Ship Network Predictor ("Seer") on nightly, using HTTP cache instead of SQLite ({{bug|1009122}}) (hurley)}}
* {{ok|Ship current (hopefully final) IETF version of HTTP/2 preffed on in nightly (hurley)}}
* {{ok|HTTP/2 "alt-svc" support ({{bug|1003448}}) (mcmanus)}}
* {{ok|HTTP cache: determine if revalidation is needed w/o doing I/O ({{bug|983122}}) (sworkman) }}
* {{ok|Network up/down link detection on all platforms ({{bug|939318}}) (bagder) }}
* {{ok|Implement WebSocket compression extension ({{bug|792831}}) (michal) }}

=== Mobile ===

=== A*Team ===

For full list, see [[Auto-tools/Goals/2014Q3|A-Team Goals 2014Q3]]

'''B2G'''
* {{ok|}} Run a set of performance and correctness tests per-commit to b2g-inbound on Flame devices
* {{ok|}} Get gaia-integration tests running on device
* {{ok|}} Expand the FxOS Certification Suite with 1.4 support, test automation to prevent regressions, and investigation of support for non-phone devices
* {{ok|}} Green up B2G tests on TaskCluster (joint with RelEng)

'''Developer Productivity'''
* {{ok|}} Deploy ReviewBoard for developers to start using (joint with RelEng)

'''Performance'''
* {{ok|}} Deploy new Talos tests for tp5o_scroll, webgl, webrtc, and mainthread I/O
* {{ok|}} Get Datazilla alerts to beta mode (full parity with graph server alerts) with reduced noise
* {{ok|}} Get Eideticker running against Android again with increased frequency
* {{ok|}} Run B2G Eideticker against same branch/build combinations as our other on-device perf tests
* {{ok|}} Stand up a Games Benchmarking system for webaudio tests running against Firefox and Chrome

'''Treeherder'''
* {{ok|}} Deliver performance web service for ingesting and returning performance data
* {{ok|}} Deliver a UI for viewing Talos data

'''Sheriffing'''
* {{ok|}} Fully transition sheriffing from TBPL to Treeherder

'''General Automation'''
* {{ok|}} Create weekly reports that describe how many tests have been added/disabled/enabled per suite and platform
* {{ok|}} Move reftest to mozbase
* {{ok|}} Add command executors for Marionette for Java and Python

'''Bugzilla'''
* {{done|}} Improve load time of related bugs; can decrease show_bug load times by up to 12%
* {{ok|}} Minify and concatenate JS files
* {{ok|}} Authoritative view for review history
* {{ok|}} Rewrite docs for REST API

'''Community'''
* {{ok|}} Create good_next_bugs (name can be adjusted) so once contributors are comfortable they can do more serious coding/problem solving on a project they are familiar with
* {{ok|}} Monthly review of mentored bugs and projects

=== Web Engineering ===
'''Crash stats'''
* {{ok|}} Prototype service for identifying post-crash user actions
* {{ok|}} Hardware and performance tuning for new primary data store
* {{ok|}} Remove older, redundant crash storage format from database
* {{ok|}} Improve search performance and features
* {{ok|}} Replace interfaces to deprecated external data sources
* {{ok|}} Remove barriers to community installations
'''FHR'''
* {{ok|}} Support search diversion plan
'''DXR'''
* {{ok|}} Improve infrastructure.
** For example, switch to ES backend, which will enable us to build multi-language support and parallel tree indexing.
* {{ok|}} Broaden our audience.
** Pull users away from MXR so we can shut it off. For example, add support for Rust or JS, squash MXR migration blockers.
'''l10n'''
* {{ok|}} Get l10n build logs into a searchable data store
* {{ok|}} Replace some buildbot functionality with a10n automation
'''Air Mozilla'''
* {{ok|}} Prototype support for streaming media boxes
* {{ok|}} Improve desktop user experience

[https://etherpad.mozilla.org/webeng-q32014 full list]

=== SUMO and Input ===
* {{ok|}} SUMO: Launch new offline SUMO app [Get Firefox on a Growth Trajectory]
* {{ok|}} SUMO: Develop new Community Hub to a level where it can replace legacy Karma app [Enable Communities with Impact]
* {{ok|}} SUMO: Research and prototype new experimental features (e.g. geotargeting, Instant Search, Search Suggestions) [Get Firefox on a Growth Trajectory]

* {{ok|}} Input: Improve documentation and install to lower the bar for contribution [Enable Communities with Impact]
* {{ok|}} Input: Support Heartbeat [Get Firefox on a Growth Trajectory]
* {{ok|}} Input: Dashboards for Everyone [Get Firefox on a Growth Trajectory]

=== Release Engineering - Laura ===
* {{ok|}} Enable capacity expansion for bare-metal releng OS X build and test slaves via hardware provided by third-party datacenters (Get Firefox on a Trajectory of Growth)
* {{ok|}} Simplify release engineering mobile hardware infrastructure (Get Firefox on a Trajectory of Growth)
* {{ok|}} Automate developer access to continuous integration resources to expedite debugging and standing up new job variants. (Enable Communities With Impact)
* {{ok|}} Help enable video operability on the web by providing continuous integration for Cisco Open H.264 builds. (Get Firefox on a Trajectory of Growth)

=== Release Engineering - Taras ===
* {{ok|}} Replace aging Firefox update service with a scalable, modern solution. (Get Firefox on a Trajectory of Growth)
* {{ok|}} Simplify developer workflow by automating patch landing and uplift. (Enable Communities With Impact)
* {{ok|}} Optimize network transfers for build/test automation between datacenters. (Enable Communities With Impact)
* {{ok|}} Continue AWS cost optimizations: EBS < 3% of AWS bill(vs 30% in Q2) (Enable Communities With Impact)
* {{ok|}} Improve developer workflow by migrating 80% of FirefoxOS build/test jobs to taskcluster (Enable Communities With Impact)
* {{ok|}} Turn telemetry is into a general purpose s3 ingester and analysis tool

=== Release Engineering Operations ===
* Build/Test System Performance Enhancements
** {{ok| Unify releng platform architecture, using common tools and best practices, to decrease complexity and enable smoother developer engagement {{bug|1026110}} [Get Firefox on a Trajectory of Growth, Enable Communities With Impact] }}
** {{ok| Improve communication and response time for releng network flow requests {{bug|1026112}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{ok| Improve security for all releng windows infrastructure {{bug|893716}} [Get Firefox on a Trajectory of Growth] }}
** {{done| Update windows platform developer tools {{bug|1019165}} [Get Firefox on a Trajectory of Growth] }}
* Build/Test System Self-Serve Re-architecture
** {{prev| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{drop| Create self-service capability for releng hardware Firefox linux test slaves (build slaves as a stretch goal) {{bug|1026687}} (depends on completion of previous goal) [Get Firefox on a Trajectory of Growth, Scale Firefox OS] - bare metal openstack is proving to be too bleeding edge and buggy to use for production services. We will continue to work on this project and track changes made in the opernstack code base, but we will not move any services to production }}
** {{drop| Create self-service capability for releng hardware Firefox windows test slaves. {{bug|967064}} [Get Firefox on a Growth Trajectory] - Still pending completion of 2008R2 work }}

=== Developer Services ===
* {{new|(with B-team) roll out phase 2 of new review tooling}} [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{new|Upgrade existing Mercurial infrastructure to support more rapid, safe, and coordinated deployment of updates.}} [Get Firefox on a Growth Trajectory / Enable communities with impact]

[https://etherpad.mozilla.org/devservices-Q32014 Full List]

=== Security & Privacy Engineering ===
More details here: [[SecurityEngineering/2014/Q3Goals]]

'''Content Security'''
* {{ok|Gecko Security Hooks: Finish code and debugging for New Channel API, start getting reviews}} (dri=tanvi)
* {{ok|Gecko Security Hooks: Create plan for addon compatibility}} (dri=tanvi)
* {{done|CSP: Remove old JS implementation from mozilla-central}} (dri=sstamm)
* {{new|Evangelism: Security Open Mic presentation + blog post about new CSP implementation, maybe again as brown bag.}} (dri=sstamm)
* {{ok|''[stretch goal]'' CSP: Fix majority of CSP 1.1 compatibility bugs}} (dri=ckerschb)

'''Tracking Protection'''
* {{ok|Referer: Finish implementation of <meta> referrer control with volunteer help}} (dri=sstamm)
* {{done|Land first implementation of protection in Fx 33/34 off by default.}} (dri=mmc)

'''Communications Security'''
* {{ok|SSL Error Reporting finish first implementation of ssl error reporting feature.}} (dri=grobinson)
* {{ok| HPKP - implement pinning http header}} (dri=cviecco)
* {{new| Update roadmap for Cert Revocation improvements}} (dri=rbarnes)
* {{done| Create a mechanism to provision phones with an alternate cert}} (dri=mgoodwin)
* {{ok| Add measurement/enforcement of compliance with CABF Baseline Requirements}} (dri=keeler)
* {{ok| Create a tool for testing CA certificate compliance and EV-readiness}} (dri=keeler)
* {{ok| Add support for key wrap/unwrap and ECC in WebCrypto}} (dri=rbarnes)
* {{ok| ''[stretch goal]'' Get CA Program data into one database}} (dri=kathleen)

=== Firefox and Platform Security ===

* [https://mana.mozilla.org/wiki/display/~gkwong@mozilla.com/Marifuzz Marifuzz ] fuzzer ported to and running on Flame devices.
* Update ASan and LSan work for DOMFuzzer
* Update "Bounty Stars" document with issues found by external reporters and updating DOMFuzzer to reflect these results.
* Get Clang on RelEng ready for official OS X ASan builds.
* Initial work to move CoreFuzz towards running in cloud environments.
* WebCrypto API fuzzing using Dharma fuzzer.
* Port a portion of WebRTC fuzzing from Frambois fuzzer to Dharma fuzzer.
* Peach: Improving and porting Peach 2 to Python 3.
* Public Mozilla Security Github work: Moving of fuzzing tools from Fuzzing Hg to GitHub, including work to separate harnesses from testcase generation tools.

=== Games Program ===
*Reach out to 3rd party engines en masse (also for Q4)
*Select a 3D demo for mobile
*Pick a partner demo to optimize for mobile
*Focus on supporting shipping games and maintaining platform stability
*Focus on Shared Array Buffer implementation
*WebGL Benchmarks
*Continue to work MDN documentation; get Emscripten documentation started
*GDC and MWC event support plan

=== Release Management ===
For full list, see [[Release_Management/Goals/2014Q3#Release_Management_General|Release Management 2014Q3 Goals]].
* Create and document process for Desktop/Mobile feature fast tracking
* Determine future of ESR and how to manage this channel
* Continue desktop throttling experiment with intention of reducing throttled time while maintaining existing level of feedback
* Improve release notes with revamped template for all products
* Create B2G release model proposals and gather feedback for potential changes
* Figure out what to do with B2G Security Releases

===Program Management===

See this wiki page for a full list of [https://wiki.mozilla.org/Program_Management/Firefox/2014-Q3-Goals Program Management goals].

* Create a set of dashboards based on the ES database to track platform projects and surface bottlenecks.
* Brown bag presentation/restropective on the agile processes we are using on Desktop and FirefoxOS.
* Evaluate and produce a report on several tools for helping organize and visualize team backlogs and priority lists; wiki, spreadsheets, Trello, Kanbanize.

=== Quality Engineering ===
See this wiki for the full list of [https://wiki.mozilla.org/QA/Goals/2014q3 Quality goals]. What follows are our brief summary of our internal improvement goals for each strategic team.
* Firefox QA - Revitalize our Quality Engineering strategy by switching to a feature-based test strategy for all Firefox browser products so that there are test plans for each feature and testing is executed within two sprints of the feature's code landing
* Firefox OS - Better metrics for quality analysis, provide opportunities for community contribution, and expanding the role of our on-device automation for reporting to Treeherder.
* Services - Ensure new offerings have 98% uptime (FxA Sync, OAuth, FMD, Loop) and no more than 2 P1 bugs discovered post launch while building a core contributor base in services
* Marketplace - Ensure Marketplace's new payments backend, in-app payments, and the Marketplace feed land with high quality releases.
* Platform QA - Deploy into continuous integration a regression testing system for WebRTC along three areas of investigation: 1. "Smoke" tests, 2. Connection tests, and 3. Connection quality tests. These will be performed in a variety of environments, including various network topologies with various performance characteristics, connections between various versions of Firefox, and connections on multiple OS platforms. Test plans will be developed, and we will measure coverage of test plans. Results will be posted and available in Treeherder. We will also build backlog for next Platform Tiger Team tasks.
* Community - Increase conversion of interested and casual contributors to help them become active contributors with strong ties to the QA community

Platform/2014-Q3-Goals

2014-08-14T09:28:22Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
Items marked [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 here] with release 33 and 34 are part of the Q3 landings.

=== Layout ===
* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Enable Vertical Text for major use cases for Chinese & Japanese
** {{ok|bug 145503}}

* Text Performance
** {{ok|{{bug|998869}}}} Streamline parsing of fontlists and improve efficiency of font matching code (note: unicode-range support will fall out of this work)
** {{ok|{{bug|934770}}}} - slow at rendering large blocks of plain text
** {{ok|{{bug|860492}}}} - Divide large text runs into smaller runs to avoid chrome hangs

* Improve Restyling Performance
** {{ok|bug 977991}}

* {{ok|Font Inflation and Reflow-on-Zoom }}
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Projects with Adobe
** {{ok|CSS Filters}}

* Animations & Transitions
** {{ok|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{ok|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|TBD}}

* CSS Scrolling
** {{ok|CSS scroll snapping}}
** {{ok|scroll-behavior:smooth}}

* CSS Flexbox
** {{ok|performance bugs}}
** {{ok|spec changes}}

* CSS Ruby
** {{ok|implementation}}

=== Media ===
* {{ok|Enable MSE/VP9 for Firefox 33 in Nightly/Aurora}}
* {{ok|Enable MSE/MP4 on Windows and Firefox OS for Firefox 34}}

=== DOM ===
* {{ok|Mirror prototype of DOM objects through xray wrappers (peterv)}}
* {{ok|Remove nsDOMClassInfo.cpp}}
* {{done|Make less-privileged non-Xrayable unwaived opaque from privileged code (bholley, {{bug|856067}})}}
* {{ok|Route all JSContext pushing through AutoJSAPI and Implement GetEntryGlobal (bobowen, bholley, {{bug|951991}})}}
* {{ok|Land <picture> preffed on on nightly ({{bug|1017875}}) (johns)}}
* {{ok|audit callsites of IsInDoc()/GetCurrentDoc to ensure correct Shadow DOM behaviour and fix Shadow DOM blockers for Gaia (smaug, wchen) ({{bug|1026047}})}}
* {{ok|land Service Workers preffed on on nightly (nsm, bkelly, baku) ({{bug|903441}})}}

=== WebAPI ===
* {{ok|create design plan for "share" activity (flow, what kind of objects are involved) (annevk)}}
* {{ok|document existing activities usage in gaia (ehsan)}}
* {{ok|get [https://w3c.github.io/screen-orientation/ screen orientation spec] to LC (marcosc)}}
* {{ok|publish use cases and spec for [http://w3c.github.io/screen-wake/ "wakelock" API] (marcosc)}}
* {{ok|24/12 hour format API (ehsan) {{bug|903683}}}}
* {{ok|{{bug|942542}} new quota API on PBackground for Service Worker cache (janv)}}
* {{ok|{{bug|701634}} IndexedDB in workers (bent)}}

=== JS ===
* {{jok|837314}} ES6 classes
* {{jok|941796}} Generational GC on Firefox OS
* {{jok|650161}} Compacting GC to reduce memory usage
* {{jok|856533}} Escape analysis JIT optimizations
* {{jok|998392}} Use Latin1 strings to reduce memory usage
* {{jok|903519}} Allocate strings in GC nursery (for performance)
* {{jok|972710}} ARM64 JIT ''[stretch goal]''

=== Accessibility ===
* {{ok|}}e10s: proxy the common a11y API stuff like name, role, and states.
* {{ok|}}GAIA: Fix [https://bugzilla.mozilla.org/buglist.cgi?priority=--&f1=blocked&list_id=10674217&o1=anyexact&resolution=---&query_based_on=b2ga11y%20p%3D1&o2=substring&query_format=advanced&f2=status_whiteboard&v1=893789&component=Disability%20Access%20APIs&component=Gaia&component=Gaia%3A%3ABluetooth%20File%20Transfer&component=Gaia%3A%3ABrowser&component=Gaia%3A%3ABuild&component=Gaia%3A%3ACalendar&component=Gaia%3A%3ACamera&component=Gaia%3A%3AClock&component=Gaia%3A%3AContacts&component=Gaia%3A%3ACost%20Control&component=Gaia%3A%3ADialer&component=Gaia%3A%3AE-Mail&component=Gaia%3A%3AEverything.me&component=Gaia%3A%3AFirst%20Time%20Experience&component=Gaia%3A%3AFMRadio&component=Gaia%3A%3AGallery&component=Gaia%3A%3AGithubBot&component=Gaia%3A%3AHomescreen&component=Gaia%3A%3AKeyboard&component=Gaia%3A%3AL10n&component=Gaia%3A%3ALoop&component=Gaia%3A%3AMusic&component=Gaia%3A%3ANotes&component=Gaia%3A%3APDF%20Viewer&component=Gaia%3A%3APerformanceTest&component=Gaia%3A%3ARingtones&component=Gaia%3A%3ASearch&component=Gaia%3A%3ASettings&component=Gaia%3A%3ASMS&component=Gaia%3A%3ASystem&component=Gaia%3A%3ASystem%3A%3ABrowser%20Chrome&component=Gaia%3A%3ASystem%3A%3AInput%20Mgmt&component=Gaia%3A%3ASystem%3A%3ALockscreen&component=Gaia%3A%3ASystem%3A%3AWindow%20Mgmt&component=Gaia%3A%3ATestAgent&component=Gaia%3A%3AUI%20Tests&component=Gaia%3A%3AVideo&component=Gaia%3A%3AWallpaper&component=Gaia%3A%3AWappush&v2=b2ga11y%20p%3D1&product=Core&product=Firefox%20OS all Gaia P1 a11y bugs] (~30 at this time).
* {{ok|}}FFOS: {{Bug|1030465}} - Volume change should update the screen reader volume.
* {{ok|}}FFOS: {{Bug|1030466}} - Headphones screen reader volume is too low.
* {{ok|}}FFOS: {{Bug|1030468}} - VC rectangle needs to work with scaled content.
* {{ok|}}FFOS: {{Bug|1030470}} - Localization needs to work when switching locales in FxOS.

=== Perf ===

Fix major source of browser jank:

* {{ok|Initialize plugin instances asynchronously {{bug|998863}} }}
* {{ok|Pause heavy main-thread activities while user is interacting with the browser: }}
** {{ok|Determine when a user is actively interacting with the browser}}
** {{ok|Detect when jank occurs during interactions and report to Telemetry {{bug|1017055}} }}
** {{ok|Experiment with hinting to GC & CC that they should pause while the user is interacting with the browser}}
* {{ok|Help Frontend team with Places refactoring, eliminate some of the [http://telemetry.mozilla.org/slowsql/ Places main-thread SQL] reported to Telemetry }}
* {{ok|Don't store UI customization in localstore.rdf, use off-main thread JSON instead {{bug|559505}} }}

Improve Firefox startup (identified as a top issue in user research):

* {{ok|Reduce appearance of the "profile is in use" message on startup {{bug|286355}} }}
* {{ok|Restore windows one by one during session-restore {{bug|1034534}} and/or load windows by descending z-order {{bug|1034036}} }}
* {{ok|C++ version of AsyncShutdown {{bug|918317}} }}

Prevent performance regressions:

* {{ok|Implement automatic detection & alerting for Telemetry regressions {{bug|1031032}} }}
* {{ok|Help developers understand & diagnose Talos regressions}}, e.g. [https://bugzilla.mozilla.org/show_bug.cgi?id=1026550 Firefox 33 regression tracking], [https://bugzilla.mozilla.org/show_bug.cgi?id=1004427 Firefox 32 regressions], [https://bugzilla.mozilla.org/show_bug.cgi?id=990085 Firefox 31]

Grow community:

* {{ok|Mentor at least 5 external contributors}}

=== Networking ===

* {{ok|Ship Network Predictor ("Seer") on nightly, using HTTP cache instead of SQLite ({{bug|1009122}}) (hurley)}}
* {{ok|Ship current (hopefully final) IETF version of HTTP/2 preffed on in nightly (hurley)}}
* {{ok|HTTP/2 "alt-svc" support ({{bug|1003448}}) (mcmanus)}}
* {{ok|HTTP cache: determine if revalidation is needed w/o doing I/O ({{bug|983122}}) (sworkman) }}
* {{ok|Network up/down link detection on all platforms ({{bug|939318}}) (bagder) }}
* {{ok|Implement WebSocket compression extension ({{bug|792831}}) (michal) }}

=== Mobile ===

=== A*Team ===

For full list, see [[Auto-tools/Goals/2014Q3|A-Team Goals 2014Q3]]

'''B2G'''
* {{ok|}} Run a set of performance and correctness tests per-commit to b2g-inbound on Flame devices
* {{ok|}} Get gaia-integration tests running on device
* {{ok|}} Expand the FxOS Certification Suite with 1.4 support, test automation to prevent regressions, and investigation of support for non-phone devices
* {{ok|}} Green up B2G tests on TaskCluster (joint with RelEng)

'''Developer Productivity'''
* {{ok|}} Deploy ReviewBoard for developers to start using (joint with RelEng)

'''Performance'''
* {{ok|}} Deploy new Talos tests for tp5o_scroll, webgl, webrtc, and mainthread I/O
* {{ok|}} Get Datazilla alerts to beta mode (full parity with graph server alerts) with reduced noise
* {{ok|}} Get Eideticker running against Android again with increased frequency
* {{ok|}} Run B2G Eideticker against same branch/build combinations as our other on-device perf tests
* {{ok|}} Stand up a Games Benchmarking system for webaudio tests running against Firefox and Chrome

'''Treeherder'''
* {{ok|}} Deliver performance web service for ingesting and returning performance data
* {{ok|}} Deliver a UI for viewing Talos data

'''Sheriffing'''
* {{ok|}} Fully transition sheriffing from TBPL to Treeherder

'''General Automation'''
* {{ok|}} Create weekly reports that describe how many tests have been added/disabled/enabled per suite and platform
* {{ok|}} Move reftest to mozbase
* {{ok|}} Add command executors for Marionette for Java and Python

'''Bugzilla'''
* {{done|}} Improve load time of related bugs; can decrease show_bug load times by up to 12%
* {{ok|}} Minify and concatenate JS files
* {{ok|}} Authoritative view for review history
* {{ok|}} Rewrite docs for REST API

'''Community'''
* {{ok|}} Create good_next_bugs (name can be adjusted) so once contributors are comfortable they can do more serious coding/problem solving on a project they are familiar with
* {{ok|}} Monthly review of mentored bugs and projects

=== Web Engineering ===
'''Crash stats'''
* {{ok|}} Prototype service for identifying post-crash user actions
* {{ok|}} Hardware and performance tuning for new primary data store
* {{ok|}} Remove older, redundant crash storage format from database
* {{ok|}} Improve search performance and features
* {{ok|}} Replace interfaces to deprecated external data sources
* {{ok|}} Remove barriers to community installations
'''FHR'''
* {{ok|}} Support search diversion plan
'''DXR'''
* {{ok|}} Improve infrastructure.
** For example, switch to ES backend, which will enable us to build multi-language support and parallel tree indexing.
* {{ok|}} Broaden our audience.
** Pull users away from MXR so we can shut it off. For example, add support for Rust or JS, squash MXR migration blockers.
'''l10n'''
* {{ok|}} Get l10n build logs into a searchable data store
* {{ok|}} Replace some buildbot functionality with a10n automation
'''Air Mozilla'''
* {{ok|}} Prototype support for streaming media boxes
* {{ok|}} Improve desktop user experience

[https://etherpad.mozilla.org/webeng-q32014 full list]

=== SUMO and Input ===
* {{ok|}} SUMO: Launch new offline SUMO app [Get Firefox on a Growth Trajectory]
* {{ok|}} SUMO: Develop new Community Hub to a level where it can replace legacy Karma app [Enable Communities with Impact]
* {{ok|}} SUMO: Research and prototype new experimental features (e.g. geotargeting, Instant Search, Search Suggestions) [Get Firefox on a Growth Trajectory]

* {{ok|}} Input: Improve documentation and install to lower the bar for contribution [Enable Communities with Impact]
* {{ok|}} Input: Support Heartbeat [Get Firefox on a Growth Trajectory]
* {{ok|}} Input: Dashboards for Everyone [Get Firefox on a Growth Trajectory]

=== Release Engineering - Laura ===
* {{ok|}} Enable capacity expansion for bare-metal releng OS X build and test slaves via hardware provided by third-party datacenters (Get Firefox on a Trajectory of Growth)
* {{ok|}} Simplify release engineering mobile hardware infrastructure (Get Firefox on a Trajectory of Growth)
* {{ok|}} Automate developer access to continuous integration resources to expedite debugging and standing up new job variants. (Enable Communities With Impact)
* {{ok|}} Help enable video operability on the web by providing continuous integration for Cisco Open H.264 builds. (Get Firefox on a Trajectory of Growth)

=== Release Engineering - Taras ===
* {{ok|}} Replace aging Firefox update service with a scalable, modern solution. (Get Firefox on a Trajectory of Growth)
* {{ok|}} Simplify developer workflow by automating patch landing and uplift. (Enable Communities With Impact)
* {{ok|}} Optimize network transfers for build/test automation between datacenters. (Enable Communities With Impact)
* {{ok|}} Continue AWS cost optimizations: EBS < 3% of AWS bill(vs 30% in Q2) (Enable Communities With Impact)
* {{ok|}} Improve developer workflow by migrating 80% of FirefoxOS build/test jobs to taskcluster (Enable Communities With Impact)
* {{ok|}} Turn telemetry is into a general purpose s3 ingester and analysis tool

=== Release Engineering Operations ===
* Build/Test System Performance Enhancements
** {{ok| Unify releng platform architecture, using common tools and best practices, to decrease complexity and enable smoother developer engagement {{bug|1026110}} [Get Firefox on a Trajectory of Growth, Enable Communities With Impact] }}
** {{ok| Improve communication and response time for releng network flow requests {{bug|1026112}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{ok| Improve security for all releng windows infrastructure {{bug|893716}} [Get Firefox on a Trajectory of Growth] }}
* Build/Test System Self-Serve Re-architecture
** {{prev| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{drop| Create self-service capability for releng hardware Firefox linux test slaves (build slaves as a stretch goal) {{bug|1026687}} (depends on completion of previous goal) [Get Firefox on a Trajectory of Growth, Scale Firefox OS] - bare metal openstack is proving to be too bleeding edge and buggy to use for production services. We will continue to work on this project and track changes made in the opernstack code base, but we will not move any services to production }}
** {{ok| Create self-service capability for releng hardware Firefox windows test slaves. {{bug|967064}} [Get Firefox on a Growth Trajectory] }}

=== Developer Services ===
* {{new|(with B-team) roll out phase 2 of new review tooling}} [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{new|Upgrade existing Mercurial infrastructure to support more rapid, safe, and coordinated deployment of updates.}} [Get Firefox on a Growth Trajectory / Enable communities with impact]

[https://etherpad.mozilla.org/devservices-Q32014 Full List]

=== Security & Privacy Engineering ===
More details here: [[SecurityEngineering/2014/Q3Goals]]

'''Content Security'''
* {{ok|Gecko Security Hooks: Finish code and debugging for New Channel API, start getting reviews}} (dri=tanvi)
* {{ok|Gecko Security Hooks: Create plan for addon compatibility}} (dri=tanvi)
* {{done|CSP: Remove old JS implementation from mozilla-central}} (dri=sstamm)
* {{new|Evangelism: Security Open Mic presentation + blog post about new CSP implementation, maybe again as brown bag.}} (dri=sstamm)
* {{ok|''[stretch goal]'' CSP: Fix majority of CSP 1.1 compatibility bugs}} (dri=ckerschb)

'''Tracking Protection'''
* {{ok|Referer: Finish implementation of <meta> referrer control with volunteer help}} (dri=sstamm)
* {{done|Land first implementation of protection in Fx 33/34 off by default.}} (dri=mmc)

'''Communications Security'''
* {{ok|SSL Error Reporting finish first implementation of ssl error reporting feature.}} (dri=grobinson)
* {{ok| HPKP - implement pinning http header}} (dri=cviecco)
* {{new| Update roadmap for Cert Revocation improvements}} (dri=rbarnes)
* {{done| Create a mechanism to provision phones with an alternate cert}} (dri=mgoodwin)
* {{ok| Add measurement/enforcement of compliance with CABF Baseline Requirements}} (dri=keeler)
* {{ok| Create a tool for testing CA certificate compliance and EV-readiness}} (dri=keeler)
* {{ok| Add support for key wrap/unwrap and ECC in WebCrypto}} (dri=rbarnes)
* {{ok| ''[stretch goal]'' Get CA Program data into one database}} (dri=kathleen)

=== Firefox and Platform Security ===

* [https://mana.mozilla.org/wiki/display/~gkwong@mozilla.com/Marifuzz Marifuzz ] fuzzer ported to and running on Flame devices.
* Update ASan and LSan work for DOMFuzzer
* Update "Bounty Stars" document with issues found by external reporters and updating DOMFuzzer to reflect these results.
* Get Clang on RelEng ready for official OS X ASan builds.
* Initial work to move CoreFuzz towards running in cloud environments.
* WebCrypto API fuzzing using Dharma fuzzer.
* Port a portion of WebRTC fuzzing from Frambois fuzzer to Dharma fuzzer.
* Peach: Improving and porting Peach 2 to Python 3.
* Public Mozilla Security Github work: Moving of fuzzing tools from Fuzzing Hg to GitHub, including work to separate harnesses from testcase generation tools.

=== Games Program ===
*Reach out to 3rd party engines en masse (also for Q4)
*Select a 3D demo for mobile
*Pick a partner demo to optimize for mobile
*Focus on supporting shipping games and maintaining platform stability
*Focus on Shared Array Buffer implementation
*WebGL Benchmarks
*Continue to work MDN documentation; get Emscripten documentation started
*GDC and MWC event support plan

=== Release Management ===
For full list, see [[Release_Management/Goals/2014Q3#Release_Management_General|Release Management 2014Q3 Goals]].
* Create and document process for Desktop/Mobile feature fast tracking
* Determine future of ESR and how to manage this channel
* Continue desktop throttling experiment with intention of reducing throttled time while maintaining existing level of feedback
* Improve release notes with revamped template for all products
* Create B2G release model proposals and gather feedback for potential changes
* Figure out what to do with B2G Security Releases

===Program Management===

See this wiki page for a full list of [https://wiki.mozilla.org/Program_Management/Firefox/2014-Q3-Goals Program Management goals].

* Create a set of dashboards based on the ES database to track platform projects and surface bottlenecks.
* Brown bag presentation/restropective on the agile processes we are using on Desktop and FirefoxOS.
* Evaluate and produce a report on several tools for helping organize and visualize team backlogs and priority lists; wiki, spreadsheets, Trello, Kanbanize.

=== Quality Engineering ===
See this wiki for the full list of [https://wiki.mozilla.org/QA/Goals/2014q3 Quality goals]. What follows are our brief summary of our internal improvement goals for each strategic team.
* Firefox QA - Revitalize our Quality Engineering strategy by switching to a feature-based test strategy for all Firefox browser products so that there are test plans for each feature and testing is executed within two sprints of the feature's code landing
* Firefox OS - Better metrics for quality analysis, provide opportunities for community contribution, and expanding the role of our on-device automation for reporting to Treeherder.
* Services - Ensure new offerings have 98% uptime (FxA Sync, OAuth, FMD, Loop) and no more than 2 P1 bugs discovered post launch while building a core contributor base in services
* Marketplace - Ensure Marketplace's new payments backend, in-app payments, and the Marketplace feed land with high quality releases.
* Platform QA - Deploy into continuous integration a regression testing system for WebRTC along three areas of investigation: 1. "Smoke" tests, 2. Connection tests, and 3. Connection quality tests. These will be performed in a variety of environments, including various network topologies with various performance characteristics, connections between various versions of Firefox, and connections on multiple OS platforms. Test plans will be developed, and we will measure coverage of test plans. Results will be posted and available in Treeherder. We will also build backlog for next Platform Tiger Team tasks.
* Community - Increase conversion of interested and casual contributors to help them become active contributors with strong ties to the QA community

Platform/2014-Q3-Goals

2014-07-31T15:49:45Z

Arich: /* Release Engineering Operations */

ReleaseEngineering/PuppetAgain

2014-07-24T13:18:43Z

Arich: /* Third-Party */

<div style="float: right; border: thin black solid; padding: 2em;">
A sysadmin asked the Architect,
:"What's the best way to install a new system?"
The Architect answered,
:"Turn it on."
The sysadmin was enlightened.
</div>

= Documentation - Manifests & Modules =

The Puppet manifests themselves are documented here. Any new modules should be added to the proper list below.

== Modules ==

All substantial configuration is done with puppet modules, in the <tt>modules</tt> directory. Each should have its own page describing both how to use the module, and how the module works, below:

=== Infrastructure ===

These modules are part of the puppet system itself, and provide support to other modules as needed

* [[ReleaseEngineering/PuppetAgain/Modules/config]] - global configuration
* [[ReleaseEngineering/PuppetAgain/Modules/dirs]] - Common directories
* [[ReleaseEngineering/PuppetAgain/Modules/packages]] - install packages generically
* [[ReleaseEngineering/PuppetAgain/Modules/puppet]] - install, upgrade, and run puppet (including custom facts, etc.)
* [[ReleaseEngineering/PuppetAgain/Modules/toplevel]] - top-level classes for node types, included from node definitions
* [[ReleaseEngineering/PuppetAgain/Modules/shared]] - shared calculated values, functions, facts, etc.
* [[ReleaseEngineering/PuppetAgain/Modules/users]] - user account management
* [[ReleaseEngineering/PuppetAgain/Modules/puppetmaster]] - install, upgrade and run puppet master

=== Action ===

These modules actually get stuff done.

* [[ReleaseEngineering/PuppetAgain/Modules/androidemulator]] - install and configure Android emulators
* [[ReleaseEngineering/PuppetAgain/Modules/aws_manager]] - install and manage AWS related management scripts
* [[ReleaseEngineering/PuppetAgain/Modules/bmm]] - configure all the components of a Mozpool imaging server
* [[ReleaseEngineering/PuppetAgain/Modules/bors]] - bors installation
* [[ReleaseEngineering/PuppetAgain/Modules/buildslave]] - buildslave (buildbot) installation and startup
* [[ReleaseEngineering/PuppetAgain/Modules/buildmaster]] - buildmaster (buildbot) installation and startup
* [[ReleaseEngineering/PuppetAgain/Modules/ccache]] - ccache directory management
* [[ReleaseEngineering/PuppetAgain/Modules/clean]] - cleanup tasks
* [[ReleaseEngineering/PuppetAgain/Modules/collectd]] - configure collectd
* [[ReleaseEngineering/PuppetAgain/Modules/cron]] - install and start the cron daemon
* [[ReleaseEngineering/PuppetAgain/Modules/disableservices]] - disable unneeded services
* [[ReleaseEngineering/PuppetAgain/Modules/foopy]] - build foopies
* [[ReleaseEngineering/PuppetAgain/Modules/fw]] - simple interface for host firewall configuration
* [[ReleaseEngineering/PuppetAgain/Modules/gaia_bumper]] - bump gaia (nicely, of course)
* [[ReleaseEngineering/PuppetAgain/Modules/ganglia]] - configure ganglia
* [[ReleaseEngineering/PuppetAgain/Modules/gui]] - configure a GUI environment
* [[ReleaseEngineering/PuppetAgain/Modules/hardware]] - hardware-specific stuff
* [[ReleaseEngineering/PuppetAgain/Modules/httpd]] - install and configure httpd server
* [[ReleaseEngineering/PuppetAgain/Modules/mercurial]] - manage hg repositories
* [[ReleaseEngineering/PuppetAgain/Modules/mockbuild]] - manage mock build environments
* [[ReleaseEngineering/PuppetAgain/Modules/mozpool]] - configure all the components of a Mozpool server
* [[ReleaseEngineering/PuppetAgain/Modules/needs_reboot]] - handle reasons that a system might need to be rebooted
* [[ReleaseEngineering/PuppetAgain/Modules/network]] - configure host networking parameters
* [[ReleaseEngineering/PuppetAgain/Modules/nrpe]] - NRPE support
* [[ReleaseEngineering/PuppetAgain/Modules/ntp]] - NTP support
* [[ReleaseEngineering/PuppetAgain/Modules/pkgbuilder]] - set up a host to build OS packages
* [[ReleaseEngineering/PuppetAgain/Modules/powermanagement]] - configure power management
* [[ReleaseEngineering/PuppetAgain/Modules/releaserunner]] - install release runner
* [[ReleaseEngineering/PuppetAgain/Modules/rsyslog]] - rsyslog configuration
* [[ReleaseEngineering/PuppetAgain/Modules/runner]] - install runner and manage pre-flight tasks
* [[ReleaseEngineering/PuppetAgain/Modules/screenresolution]] - set GUI screen resolution
* [[ReleaseEngineering/PuppetAgain/Modules/selfserve_agent]] - install the BuildAPI self-serve agent
* [[ReleaseEngineering/PuppetAgain/Modules/signingserver]] - configure a signing server instance
* [[ReleaseEngineering/PuppetAgain/Modules/slaveapi]] - configure a slaveapi server instance
* [[ReleaseEngineering/PuppetAgain/Modules/slave_secrets]] - add secrets to slaves
* [[ReleaseEngineering/PuppetAgain/Modules/smarthost]] - configure a mail relay
* [[ReleaseEngineering/PuppetAgain/Modules/ssh]] - manage ssh configuration (server, global, and user)
* [[ReleaseEngineering/PuppetAgain/Modules/talos]] - talos slave specific settings
* [[ReleaseEngineering/PuppetAgain/Modules/tftpd]] - tftpd (and xinetd) configuration
* [[ReleaseEngineering/PuppetAgain/Modules/timezone]] - set the system timezone
* [[ReleaseEngineering/PuppetAgain/Modules/tweaks]] - small, one-off classes (aka "miscellaneous")
* [[ReleaseEngineering/PuppetAgain/Modules/vnc]] - configure the VNC server
* [[ReleaseEngineering/PuppetAgain/Modules/web_proxy]] - configure the system to use a proxy to access the web

=== Utility ===

These modules are more generic, and probably useful outside of PuppetAgain.
* [[ReleaseEngineering/PuppetAgain/Modules/kernelmodule]] - install a Linux kernel module
* [[ReleaseEngineering/PuppetAgain/Modules/motd]] - edit the contents of /etc/motd
* [[ReleaseEngineering/PuppetAgain/Modules/osxutils]] - utility for reading and writing configuration using defaults and system setup on MacOSx
* [[ReleaseEngineering/PuppetAgain/Modules/python]] - support for installing python virtualenvs and packages
* [[ReleaseEngineering/PuppetAgain/Modules/shellprofile]] - add items to users' default shell profile
* [[ReleaseEngineering/PuppetAgain/Modules/sudoers]] - manage sudo permissions
* [[ReleaseEngineering/PuppetAgain/Modules/supervisord]] - supervise processes

=== Third-Party ===

These are modules taken from elsewhere. When adding, remember to verify license compatibility and ensure proper credit.

* assert - from https://github.com/binford2k/puppet-assert
* sysctl - from https://github.com/duritong/puppet-sysctl
* concat - from https://github.com/ripienaar/puppet-concat (modified to not use a fact, although this should probably be reverted)
* firewall - from https://github.com/puppetlabs/puppetlabs-firewall/
* stdlib - from https://github.com/puppetlabs/puppetlabs-stdlib/
* vmwaretools - from https://github.com/craigwatson/puppet-vmwaretools

== Bugs ==

Bugs for work on PuppetAgain should be filed in the [https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=nobody%40mozilla.org&attach_text=&blocked=&bug_file_loc=http%3A%2F%2F&bug_severity=normal&bug_status=NEW&comment=&component=RelOps%3A%20Puppet&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&defined_groups=1&dependson=&description=&flag_type-354=X&flag_type-4=X&flag_type-407=X&flag_type-481=X&flag_type-607=X&flag_type-674=X&flag_type-707=X&flag_type-791=X&flag_type-800=X&flag_type-811=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=All&priority=--&product=Infrastructure%20%26%20Operations&qa_contact=dustin%40mozilla.com&rep_platform=All&requestee_type-4=&requestee_type-607=&requestee_type-791=&requestee_type-800=&short_desc=&status_whiteboard=&target_milestone=---&version=other Infrastructure & Operations - Relops: Puppet] Component.

= How To =

* [[ReleaseEngineering/PuppetAgain/HowTo/Re-issue Certificates for a host]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Set up a user environment]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Add new secrets]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Bootstrap a Puppetmaster]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Remove a Puppetmaster]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Change secrets]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Build RPMs]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Build DMGs]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Build DEBs]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Hack on PuppetAgain]] (patch/review guidelines)
* [[ReleaseEngineering/PuppetAgain/HowTo/Anchor Classes]] (getting dependencies right)
* [[ReleaseEngineering/PuppetAgain/HowTo/Add Files to Data]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Merge Changes Between Repos]]
* [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Read_Releng-Shared_Emails How To read releng-shared Emails] (moco releng-only)

= System Description =

This section describes how PuppetAgain is built at Mozilla. External implementations may not have all of these bells and whistles. [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=22381625 This link] contains details oriented toward Mozilla IT and ops folks.

== The Goals ==

* PuppetAgain should be usable as a whole for folks outside of Mozilla, Inc. who want to build similar systems (see "Organizations" below)
* Client images should proceed automatically from base image install to a fully-operational state. While refimages may be employed, this is done only as an optimization.
* We do not keep distinct reference images. Reference images are used only as an optimization to avoid pounding the puppet servers when installing dozens of new hosts. When a new refimage snapshot needs to be made, a fresh machine is rebuilt from scratch, snapshotted, and then returned to service.
* OS does not imply role. Roles are defined in node declarations, by including <tt>toplevel::*</tt> classes.
* Include all necessary dependencies. Debugging dependency errors when building a new reference system is no fun.
* Documentation (here) is a part of the patch.
See [[ReleaseEngineering/PuppetAgain/HowTo/Hack on PuppetAgain]] for more detail

== Organizations ==

Each distinct instance of puppetagain is referred to as an organization, and tagged with a short identifier (e.g., "moco" for the mozilla releng instance, or "seamonkey" for seamonkey). Within an organization, configuration and secrets are shared, and everything runs from the same set of manifests. Configuration and secrets can differ between organizations.

== Puppetmasters ==

PuppetAgain masters are managed by PuppetAgain. Each organization can have 1 or more masters, arranged in a cluster (with one cluster per organization). There is one "distinguished master" in the cluster. This master is distinguished only for purposes of simplifying synchronization -- the cluster will continue to operate indefinitely without the distinguished master, although master-master communication (secrets and CRLs) will not work.

See the following for more details, noting that most of this is not required for an external PuppetAgain implementation.
* [[ReleaseEngineering/PuppetAgain/Puppetmasters]]
* [[ReleaseEngineering/PuppetAgain/Puppetization Process]]
* [[ReleaseEngineering/PuppetAgain/Certificate Chaining]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Bootstrap a Puppetmaster]]

== Puppet Versions ==

The releng puppet infrastructure will strive to keep up to date with the most recent stable versions released by Puppet Labs.

== Base Images and Puppetizing ==

The base images for this infrastructure are barely-modified OS installs. They have just enough installed that they can connect to a puppet server, get certificates, and puppetize on boot.

* [[ReleaseEngineering/PuppetAgain/Base Images]]
* [[ReleaseEngineering/PuppetAgain/Puppetization Process]]

Note that, while most of PuppetAgain is intended to be easily replicated, the deployment system is probably not easily replicated, and is best left out of any external implementations.

== Custom Facts, Functions, Types, and Providers ==

Custom code is documented in the page for the module that contains it. Code that doesn't have a more appropriate home is in [[ReleaseEngineering/PuppetAgain/Modules/shared|shared]].

== Stages ==
Stages need to be defined globally in Puppet manifests, and this is done in <tt>manifests/stages.pp</tt>. The following stages are available, aside from 'main', the default stage.

* network - This stage should handle any network related configurations for some specific cases (like AWS)
* packagesetup - This stage should handle any preliminaries required for package installations, so that subsequent package installations do not need to require them explicitly.
* users - This stage creates user accounts; while this is normally automatically required, the requirement doesn't work with the temporary 'darwinuser' type.

== Nodes ==

<tt>manifests/nodes.pp</tt> defines all of the nodes the puppet masters recognize. Note that all nodes are defined for all masters. This file is a symlink to <tt>$org-nodes.pp</tt>, e.g., <tt>moco-nodes.pp</tt>. With this arrangement, each organization can make node changes without any risk to other organizations.

In anticipation of using an external node classifier (ENC), node definitions should only include classes - do not define any resources within nodes. In general, the included classes should be in the [[ReleaseEngineering/Puppet/Modules/toplevel|toplevel]] module.

Host-specific values are specified as node-scope variables, as these are easier to represent in an ENC. Such variables (including some Puppet gotchas) are described in [[ReleaseEngineering/PuppetAgain/node-scope variables|node-scope variables]].

Node definitions also specify a host's [[ReleaseEngineering/PuppetAgain/Aspects|aspects]], e.g., <tt>$aspects = [ 'staging' ]</tt>.

== Configuration ==

Per-organization configuration is read from <tt>manifests/config.pp</tt>, which is a symlink to <tt>$org-config.pp</tt>, similar to that for nodes. The <tt>config.pp</tt> file defines a "config" class that inherits from "config::base". It is free to express the configuration using any mechanism available to puppet. For some organizations, simple puppet literals will do, while more complex organizations will want to perform some more sophisticated automatic generation of configuration. See [[ReleaseEngineering/PuppetAgain/Modules/config|config]] for more.

== Secrets and External Data ==
See [[ReleaseEngineering/PuppetAgain/Secrets]] and [[ReleaseEngineering/PuppetAgain/Extsync]].

== Data ==

Puppet deals with a lot of big files - packages, mostly. We don't want these in hg! They are instead managed as data. This means several big file trees available at http://repos/$treename and, from puppet, at puppet://$treename. See [[ReleaseEngineering/PuppetAgain/Data]] for details on what's available, how it is implemented, and some how-tos.

This data is available outside of Mozilla via HTTP and rsync at http://puppetagain.pub.build.mozilla.org/data and rsync://puppetagain.pub.build.mozilla.org/data.

== Packages ==

See [[ReleaseEngineering/PuppetAgain/Packages]] for information about proper handling of packages in PuppetAgain.

== Aspects ==

Taking a page from [http://en.wikipedia.org/wiki/Aspect-oriented_programming Aspect Oriented Programming], PuppetAgain implements Aspect Oriented Puppet. Aspects cross-cut the concerns represented by the toplevel hierarchy. For example, whether a host is a staging host, whether it is loaned out, etc. See [[ReleaseEngineering/PuppetAgain/Aspects]] for details.

== Source Code ==

The manifests are at http://hg.mozilla.org/build/puppet.

= History =

Releng once used [[ReleaseEngineering/Puppet|a puppet infrastructure]] based on Puppet-0.24.8, and manifests at http://hg.mozilla.org/build/puppet-manifests/. This had a few weaknesses:
* lots of assumptions and fragile dependencies based on bugs in 0.24.8
* very few modules - mostly manifest files, organized per slave type, rather than per service/purpose
* many references to external files which are not as available as the repo itself
* puppet manifests assume some manual ref-image steps; external exact reproduction is extremely difficult

Dustin started work on a new puppet deployment - chronicled at [[User:Djmitche/New Releng Puppet Infrastructure]]. That's this puppet.

Platform/2014-Q3-Goals

2014-07-07T20:25:46Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===

=== Layout ===

=== Media ===

=== DOM ===
* {{ok|Mirror prototype of DOM objects through xray wrappers (peterv)}}
* {{ok|Remove nsDOMClassInfo.cpp}}
* {{ok|Make less-privileged non-Xrayable unwaived opaque from privileged code ({{bug|856067}})}}
* {{ok|Route all JSContext pushing through AutoJSAPI and Implement GetEntryGlobal ({{bug|951991}})}}

=== WebAPI ===

=== JS ===
* {{jok|837314}} ES6 classes
* {{jok|941796}} Generational GC on Firefox OS
* {{jok|650161}} Compacting GC to reduce memory usage
* {{jok|856533}} Escape analysis JIT optimizations
* {{jok|998392}} Use Latin1 strings to reduce memory usage
* {{jok|903519}} Allocate strings in GC nursery (for performance)
* {{jok|972710}} ARM64 JIT ''[stretch goal]''

=== Accessibility ===
* {{ok|}}e10s: proxy the common a11y API stuff like name, role, and states.
* {{ok|}}GAIA: Fix [https://bugzilla.mozilla.org/buglist.cgi?priority=--&f1=blocked&list_id=10674217&o1=anyexact&resolution=---&query_based_on=b2ga11y%20p%3D1&o2=substring&query_format=advanced&f2=status_whiteboard&v1=893789&component=Disability%20Access%20APIs&component=Gaia&component=Gaia%3A%3ABluetooth%20File%20Transfer&component=Gaia%3A%3ABrowser&component=Gaia%3A%3ABuild&component=Gaia%3A%3ACalendar&component=Gaia%3A%3ACamera&component=Gaia%3A%3AClock&component=Gaia%3A%3AContacts&component=Gaia%3A%3ACost%20Control&component=Gaia%3A%3ADialer&component=Gaia%3A%3AE-Mail&component=Gaia%3A%3AEverything.me&component=Gaia%3A%3AFirst%20Time%20Experience&component=Gaia%3A%3AFMRadio&component=Gaia%3A%3AGallery&component=Gaia%3A%3AGithubBot&component=Gaia%3A%3AHomescreen&component=Gaia%3A%3AKeyboard&component=Gaia%3A%3AL10n&component=Gaia%3A%3ALoop&component=Gaia%3A%3AMusic&component=Gaia%3A%3ANotes&component=Gaia%3A%3APDF%20Viewer&component=Gaia%3A%3APerformanceTest&component=Gaia%3A%3ARingtones&component=Gaia%3A%3ASearch&component=Gaia%3A%3ASettings&component=Gaia%3A%3ASMS&component=Gaia%3A%3ASystem&component=Gaia%3A%3ASystem%3A%3ABrowser%20Chrome&component=Gaia%3A%3ASystem%3A%3AInput%20Mgmt&component=Gaia%3A%3ASystem%3A%3ALockscreen&component=Gaia%3A%3ASystem%3A%3AWindow%20Mgmt&component=Gaia%3A%3ATestAgent&component=Gaia%3A%3AUI%20Tests&component=Gaia%3A%3AVideo&component=Gaia%3A%3AWallpaper&component=Gaia%3A%3AWappush&v2=b2ga11y%20p%3D1&product=Core&product=Firefox%20OS all Gaia P1 a11y bugs] (~30 at this time).
* {{ok|}}FFOS: {{Bug|1030465}} - Volume change should update the screen reader volume.
* {{ok|}}FFOS: {{Bug|1030466}} - Headphones screen reader volume is too low.
* {{ok|}}FFOS: {{Bug|1030468}} - VC rectangle needs to work with scaled content.
* {{ok|}}FFOS: {{Bug|1030470}} - Localization needs to work when switching locales in FxOS.

=== Perf ===

=== Networking ===

=== Mobile ===

=== A*Team ===

For full list, see [[Auto-tools/Goals/2014Q3|A-Team Goals 2014Q3]]

'''B2G'''
* {{ok|}} Run a set of performance and correctness tests per-commit to b2g-inbound on Flame devices
* {{ok|}} Get gaia-integration tests running on device
* {{ok|}} Expand the FxOS Certification Suite with 1.4 support, test automation to prevent regressions, and investigation of support for non-phone devices
* {{ok|}} Green up B2G tests on TaskCluster (joint with RelEng)

'''Developer Productivity'''
* {{ok|}} Deploy ReviewBoard for developers to start using (joint with RelEng)

'''Performance'''
* {{ok|}} Deploy new Talos tests for tp5o_scroll, webgl, webrtc, and mainthread I/O
* {{ok|}} Get Datazilla alerts to beta mode (full parity with graph server alerts) with reduced noise
* {{ok|}} Get Eideticker running against Android again with increased frequency
* {{ok|}} Run B2G Eideticker against same branch/build combinations as our other on-device perf tests
* {{ok|}} Stand up a Games Benchmarking system for webaudio tests running against Firefox and Chrome

'''Treeherder'''
* {{ok|}} Deliver performance web service for ingesting and returning performance data
* {{ok|}} Deliver a UI for viewing Talos data

'''Sheriffing'''
* {{ok|}} Fully transition sheriffing from TBPL to Treeherder

'''General Automation'''
* {{ok|}} Create weekly reports that describe how many tests have been added/disabled/enabled per suite and platform
* {{ok|}} Move reftest to mozbase
* {{ok|}} Add command executors for Marionette for Java and Python

'''Bugzilla'''
* {{ok|}} Improve load time of related bugs; can decrease show_bug load times by up to 12%
* {{ok|}} Minify and concatenate JS files
* {{ok|}} Authoritative view for review history
* {{ok|}} Rewrite docs for REST API

'''Community'''
* {{ok|}} Create good_next_bugs (name can be adjusted) so once contributors are comfortable they can do more serious coding/problem solving on a project they are familiar with
* {{ok|}} Monthly review of mentored bugs and projects

=== Web Engineering ===

=== SUMO and Input ===

=== Release Engineering ===
* Enable capacity expansion for bare-metal releng OS X build and test slaves via hardware provided by third-party datacenters (Get Firefox on a Trajectory of Growth)
* Simplify release engineering mobile hardware infrastructure (Get Firefox on a Trajectory of Growth)
* Automate developer access to continuous integration resources to expedite debugging and standing up new job variants. (Enable Communities With Impact)
* Help enable video operability on the web by providing continuous integration for Cisco Open H.264 builds. (Get Firefox on a Trajectory of Growth)
* Replace aging Firefox update service with a scaleable, modern solution. (Get Firefox on a Trajectory of Growth)
* Simplify developer workflow by automating patch landing and uplift. (Enable Communities With Impact)

=== Release Engineering Operations ===
* Build/Test System Performance Enhancements
** {{ok| Unify releng platform architecture, using common tools and best practices, to decrease complexity and enable smoother developer engagement {{bug|1026109}} and {{bug|1026110}} [Get Firefox on a Trajectory of Growth, Enable Communities With Impact] }}
** {{ok| Improve communication and response time for releng network flow requests {{bug|1026112}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{ok| Improve security for all releng windows infrastructure {{bug|893716}} [Get Firefox on a Trajectory of Growth] }}
* Build/Test System Self-Serve Re-architecture
** {{prev| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{ok| Create self-service capability for releng hardware Firefox linux test slaves (build slaves as a stretch goal) {{bug|1026687}} (depends on completion of previous goal) [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{ok| Create self-service capability for releng hardware Firefox windows test slaves. {{bug|967064}} [Get Firefox on a Growth Trajectory] }}

=== Developer Services ===

=== Security & Privacy Engineering ===
More details here: [[SecurityEngineering/2014/Q3Goals]]

'''Content Security'''
* {{new|Gecko Security Hooks: Finish code and debugging for New Channel API, start getting reviews}} (dri=tanvi)
* {{new|Gecko Security Hooks: Create plan for addon compatibility}} (dri=tanvi)
* {{new|CSP: Remove old JS implementation from mozilla-central}} (dri=sstamm)
* {{new|Evangelism: Security Open Mic presentation + blog post about new CSP implementation, maybe again as brown bag.}} (dri=sstamm)
* {{new|''[stretch goal]'' CSP: Fix majority of CSP 1.1 compatibility bugs}} (dri=ckerschb)

'''Tracking Protection'''
* {{new|Referer: Finish implementation of <meta> referrer control with volunteer help}} (dri=sstamm)
* {{new|Land first implementation of protection in Fx 33/34 off by default.}} (dri=mmc)

'''Communications Security'''
* {{prev|SSL Error Reporting finish first implementation of ssl error reporting feature.}} (dri=grobinson)
* {{new| HPKP - implement pinning http header}} (dri=cviecco)
* {{new| Update roadmap for Cert Revocation improvements}} (dri=rbarnes)
* {{new| Create a mechanism to provision phones with an alternate cert}} (dri=mgoodwin)
* {{new| Add measurement/enforcement of compliance with CABF Baseline Requirements}} (dri=keeler)
* {{new| Create a tool for testing CA certificate compliance and EV-readiness}} (dri=keeler)
* {{new| Add support for key wrap/unwrap and ECC in WebCrypto}} (dri=rbarnes)
* {{new| ''[stretch goal]'' Get CA Program data into one database}} (dri=kathleen)

=== Firefox and Platform Security ===

* [https://mana.mozilla.org/wiki/display/~gkwong@mozilla.com/Marifuzz Marifuzz ] fuzzer ported to and running on Flame devices.
* Update ASan and LSan work for DOMFuzzer
* Update "Bounty Stars" document with issues found by external reporters and updating DOMFuzzer to reflect these results.
* Get Clang on RelEng ready for official OS X ASan builds.
* Initial work to move CoreFuzz towards running in cloud environments.
* WebCrypto API fuzzing using Dharma fuzzer.
* Port a portion of WebRTC fuzzing from Frambois fuzzer to Dharma fuzzer.
* Peach: Improving and porting Peach 2 to Python 3.
* Public Mozilla Security Github work: Moving of fuzzing tools from Fuzzing Hg to GitHub, including work to separate harnesses from testcase generation tools.

=== Games Program ===

=== Release Management ===
For full list, see [[Release_Management/Goals/2014Q3#Release_Management_General|Release Management 2014Q3 Goals]].
* Create and document process for Desktop/Mobile feature fast tracking
* Determine future of ESR and how to manage this channel
* Continue desktop throttling experiment with intention of reducing throttled time while maintaining existing level of feedback
* Improve release notes with revamped template for all products
* Create B2G release model proposals and gather feedback for potential changes
* Figure out what to do with B2G Security Releases

Platform/2014-Q3-Goals

2014-07-07T20:04:35Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===

=== Layout ===

=== Media ===

=== DOM ===
* {{ok|Mirror prototype of DOM objects through xray wrappers (peterv)}}
* {{ok|Remove nsDOMClassInfo.cpp}}
* {{ok|Make less-privileged non-Xrayable unwaived opaque from privileged code ({{bug|856067}})}}
* {{ok|Route all JSContext pushing through AutoJSAPI and Implement GetEntryGlobal ({{bug|951991}})}}

=== WebAPI ===

=== JS ===
* {{jok|837314}} ES6 classes
* {{jok|941796}} Generational GC on Firefox OS
* {{jok|650161}} Compacting GC to reduce memory usage
* {{jok|856533}} Escape analysis JIT optimizations
* {{jok|998392}} Use Latin1 strings to reduce memory usage
* {{jok|903519}} Allocate strings in GC nursery (for performance)
* {{jok|972710}} ARM64 JIT ''[stretch goal]''

=== Accessibility ===
* {{ok|}}e10s: proxy the common a11y API stuff like name, role, and states.
* {{ok|}}GAIA: Fix [https://bugzilla.mozilla.org/buglist.cgi?priority=--&f1=blocked&list_id=10674217&o1=anyexact&resolution=---&query_based_on=b2ga11y%20p%3D1&o2=substring&query_format=advanced&f2=status_whiteboard&v1=893789&component=Disability%20Access%20APIs&component=Gaia&component=Gaia%3A%3ABluetooth%20File%20Transfer&component=Gaia%3A%3ABrowser&component=Gaia%3A%3ABuild&component=Gaia%3A%3ACalendar&component=Gaia%3A%3ACamera&component=Gaia%3A%3AClock&component=Gaia%3A%3AContacts&component=Gaia%3A%3ACost%20Control&component=Gaia%3A%3ADialer&component=Gaia%3A%3AE-Mail&component=Gaia%3A%3AEverything.me&component=Gaia%3A%3AFirst%20Time%20Experience&component=Gaia%3A%3AFMRadio&component=Gaia%3A%3AGallery&component=Gaia%3A%3AGithubBot&component=Gaia%3A%3AHomescreen&component=Gaia%3A%3AKeyboard&component=Gaia%3A%3AL10n&component=Gaia%3A%3ALoop&component=Gaia%3A%3AMusic&component=Gaia%3A%3ANotes&component=Gaia%3A%3APDF%20Viewer&component=Gaia%3A%3APerformanceTest&component=Gaia%3A%3ARingtones&component=Gaia%3A%3ASearch&component=Gaia%3A%3ASettings&component=Gaia%3A%3ASMS&component=Gaia%3A%3ASystem&component=Gaia%3A%3ASystem%3A%3ABrowser%20Chrome&component=Gaia%3A%3ASystem%3A%3AInput%20Mgmt&component=Gaia%3A%3ASystem%3A%3ALockscreen&component=Gaia%3A%3ASystem%3A%3AWindow%20Mgmt&component=Gaia%3A%3ATestAgent&component=Gaia%3A%3AUI%20Tests&component=Gaia%3A%3AVideo&component=Gaia%3A%3AWallpaper&component=Gaia%3A%3AWappush&v2=b2ga11y%20p%3D1&product=Core&product=Firefox%20OS all Gaia P1 a11y bugs] (~30 at this time).
* {{ok|}}FFOS: {{Bug|1030465}} - Volume change should update the screen reader volume.
* {{ok|}}FFOS: {{Bug|1030466}} - Headphones screen reader volume is too low.
* {{ok|}}FFOS: {{Bug|1030468}} - VC rectangle needs to work with scaled content.
* {{ok|}}FFOS: {{Bug|1030470}} - Localization needs to work when switching locales in FxOS.

=== Perf ===

=== Networking ===

=== Mobile ===

=== A*Team ===

For full list, see [[Auto-tools/Goals/2014Q3|A-Team Goals 2014Q3]]

'''B2G'''
* {{ok|}} Run a set of performance and correctness tests per-commit to b2g-inbound on Flame devices
* {{ok|}} Get gaia-integration tests running on device
* {{ok|}} Expand the FxOS Certification Suite with 1.4 support, test automation to prevent regressions, and investigation of support for non-phone devices
* {{ok|}} Green up B2G tests on TaskCluster (joint with RelEng)

'''Developer Productivity'''
* {{ok|}} Deploy ReviewBoard for developers to start using (joint with RelEng)

'''Performance'''
* {{ok|}} Deploy new Talos tests for tp5o_scroll, webgl, webrtc, and mainthread I/O
* {{ok|}} Get Datazilla alerts to beta mode (full parity with graph server alerts) with reduced noise
* {{ok|}} Get Eideticker running against Android again with increased frequency
* {{ok|}} Run B2G Eideticker against same branch/build combinations as our other on-device perf tests
* {{ok|}} Stand up a Games Benchmarking system for webaudio tests running against Firefox and Chrome

'''Treeherder'''
* {{ok|}} Deliver performance web service for ingesting and returning performance data
* {{ok|}} Deliver a UI for viewing Talos data

'''Sheriffing'''
* {{ok|}} Fully transition sheriffing from TBPL to Treeherder

'''General Automation'''
* {{ok|}} Create weekly reports that describe how many tests have been added/disabled/enabled per suite and platform
* {{ok|}} Move reftest to mozbase
* {{ok|}} Add command executors for Marionette for Java and Python

'''Bugzilla'''
* {{ok|}} Improve load time of related bugs; can decrease show_bug load times by up to 12%
* {{ok|}} Minify and concatenate JS files
* {{ok|}} Authoritative view for review history
* {{ok|}} Rewrite docs for REST API

'''Community'''
* {{ok|}} Create good_next_bugs (name can be adjusted) so once contributors are comfortable they can do more serious coding/problem solving on a project they are familiar with
* {{ok|}} Monthly review of mentored bugs and projects

=== Web Engineering ===

=== SUMO and Input ===

=== Release Engineering ===

=== Release Engineering Operations ===
* Build/Test System Performance Enhancements
** {{ok| Eliminate dependency on builds-4hr.js {{bug|1026109}} [Get Firefox on a Trajectory of Growth, Enable Communities With Impact] }}
** {{ok| Migrate buildapi to relengapi {{bug|1026110}} [Get Firefox on a Trajectory of Growth, Enable Communities With Impact] }}
** {{ok| Improve communication and response time for releng network flow requests {{bug|1026112}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{ok| Audit and remediation of windows OS/network security issues {{bug|893716}} [Get Firefox on a Trajectory of Growth] }}
* Build/Test System Self-Serve Re-architecture
** {{prev| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{ok| Deploy openstack bare metal imaging to production for ubuntu (stretch goal of centos) {{bug|1026687}} [Get Firefox on a Trajectory of Growth, Scale Firefox OS] }}
** {{ok| Develop a new image creation solution for W7 and W8 test machines which can be used to deploy on bare metal. {{bug|967064}} [Get Firefox on a Growth Trajectory] }}

=== Developer Services ===

=== Security & Privacy Engineering ===
More details here: [[SecurityEngineering/2014/Q3Goals]]

'''Content Security'''
* {{new|Gecko Security Hooks: Finish code and debugging for New Channel API, start getting reviews}} (dri=tanvi)
* {{new|Gecko Security Hooks: Create plan for addon compatibility}} (dri=tanvi)
* {{new|CSP: Remove old JS implementation from mozilla-central}} (dri=sstamm)
* {{new|Evangelism: Security Open Mic presentation + blog post about new CSP implementation, maybe again as brown bag.}} (dri=sstamm)
* {{new|''[stretch goal]'' CSP: Fix majority of CSP 1.1 compatibility bugs}} (dri=ckerschb)

'''Tracking Protection'''
* {{new|Referer: Finish implementation of <meta> referrer control with volunteer help}} (dri=sstamm)
* {{new|Land first implementation of protection in Fx 33/34 off by default.}} (dri=mmc)

'''Communications Security'''
* {{prev|SSL Error Reporting finish first implementation of ssl error reporting feature.}} (dri=grobinson)
* {{new| HPKP - implement pinning http header}} (dri=cviecco)
* {{new| Update roadmap for Cert Revocation improvements}} (dri=rbarnes)
* {{new| Create a mechanism to provision phones with an alternate cert}} (dri=mgoodwin)
* {{new| Add measurement/enforcement of compliance with CABF Baseline Requirements}} (dri=keeler)
* {{new| Create a tool for testing CA certificate compliance and EV-readiness}} (dri=keeler)
* {{new| Add support for key wrap/unwrap and ECC in WebCrypto}} (dri=rbarnes)
* {{new| ''[stretch goal]'' Get CA Program data into one database}} (dri=kathleen)

=== Firefox and Platform Security ===

* [https://mana.mozilla.org/wiki/display/~gkwong@mozilla.com/Marifuzz Marifuzz ] fuzzer ported to and running on Flame devices.
* Update ASan and LSan work for DOMFuzzer
* Update "Bounty Stars" document with issues found by external reporters and updating DOMFuzzer to reflect these results.
* Get Clang on RelEng ready for official OS X ASan builds.
* Initial work to move CoreFuzz towards running in cloud environments.
* WebCrypto API fuzzing using Dharma fuzzer.
* Port a portion of WebRTC fuzzing from Frambois fuzzer to Dharma fuzzer.
* Peach: Improving and porting Peach 2 to Python 3.
* Public Mozilla Security Github work: Moving of fuzzing tools from Fuzzing Hg to GitHub, including work to separate harnesses from testcase generation tools.

=== Games Program ===

=== Release Management ===
For full list, see [[Release_Management/Goals/2014Q3#Release_Management_General|Release Management 2014Q3 Goals]].
* Create and document process for Desktop/Mobile feature fast tracking
* Determine future of ESR and how to manage this channel
* Continue desktop throttling experiment with intention of reducing throttled time while maintaining existing level of feedback
* Improve release notes with revamped template for all products
* Create B2G release model proposals and gather feedback for potential changes
* Figure out what to do with B2G Security Releases

Platform/2014-Q2-Goals

2014-07-01T17:07:08Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
Items marked [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 here] with release 31 and 32 are part of the Q2 landings.

=== Layout ===

* {{ok|Table Rendering with DisplayLists}}

* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Vertical text: Implement Layout frame migration to logical coordinates https://etherpad.mozilla.org/css-writing-modes
** {{done|convert cross-layout classes}}

* Text Performance bugs ( https://etherpad.mozilla.org/textperfworkitems )
** {{ok|large text frames / interruptible reflow}}
** {{ok|enumerated font list fixes}}

* Improve Restyling Performance
** {{ok|bug 931668}}
** {{bug|977991}}
** {{bug|804975}}, {{bug|977594}}

* GFx work items
** {{ok|E10S BasicCompositor}}
** {{ok|GFx tiling}}
** {{ok|Accelerated Filters}}
*** spec work
*** shader & support work

* CSS Flexbox
** {{done|pagination}}
** recently-finalized spec changes (abspos, min-width, flex sizing) (874718, 984711, 985304)

* Animations & Transitions
** {{miss|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{done|test_animations covering OMTA}}
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{miss|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|Spec an API for querying basic properties of running CSS animations/transitions}}

* Ship and/or unprefix:
** {{done|position:sticky}}
** {{done|Font-features that need fallback support (eg. small-caps)}}

* {{miss|3D Transforms}}
** interop bugs and spec improvement (bug 976365)
** implement preserve-3d proposal
** perf work

* {{miss|Font Inflation and Reflow-on-Zoom }}
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* CSS Projects with Adobe
** {{ok|CSS Filters}}
** {{ok|CSS Masking}}
** {{ok|CSS Compositing}}

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Fonts
** {{ok|font load events}}

=== Media ===
* {{miss|Pref on MSE/VP9 for Firefox 31}}
** Expecting to land in Firefox 32 (see below)
* {{miss|Pref on MSE/VP9 for Firefox 32}}
* {{miss|Enable MSE/MP4 on Windows for Firefox 32}}
** Expecting to land on 33

=== DOM ===
* {{done|Implement Xrays to 3 out of the following: Functions ({{bug|976148}}), Objects ({{bug|987111}}), Array/Array-like ({{bug|987163}}), and Error ({{bug|987669}})}}
* {{miss|Get rid of the long tail of C++ objects that are still exposed to the web using XPConnect}}
** We had less time for this than expected due to a previous quarter missed goal taking longer than expected to finish up (now done). Everything left on this list is already moving or planned, but will flow out into Q3.
* {{done|Get LeakSanitizer builds enabled by default ({{bug|988041}})}}
* {{done|Identify and fix (DOM stuff, at least) hotspots in b2g app startup (smaug)}}
* {{miss|refactor how tokenizer and tree builder use buffers to reduce memory pressure crashes (hsivonen)}}
** Henri has spent a lot of time with other responsibilities
* {{miss|Land all non-cache bits of Service Workers preffed-off (on is a bonus) on m-c (nsm)}}
** While this goal as written is a miss the overall progress towards Service Workers is progressing very well. This missed due to us not getting other resources on this quick enough due to other responsibilities, but velocity is really good now.
* {{done|Help guide and review requestAutocomplete backend implementation ({{bug|939351}})}} (likely smaug)
** The DOM team has been responsive to requests and implementation by the Firefox team is progressing.
* {{done|implement [http://picture.responsiveimages.org/ <picture>] ({{bug|870022}}) (johns)}}
** Things are looking good for landing here now that srcset is complete.
* {{miss|Ensure plugins are shippable for e10s}} (sort of {{bug|874016}}) (johns)
** John is working on this but <picture> took more of the quarter than expected.
* {{miss|Implement Shadow DOM :host style selector ({{bug|992245}})}} (wchen)
** wchen got caught up with other Web Components issues affecting gaia so this may not happen in Q2.
* {{done|Enable Shadow DOM for certified apps ({{bug|1000199}})}} (wchen)
* {{done|Define a plan for how to instrument code that triggers COW of pages post forking in a post Nuwa world (bonus if we can actually build that tool this quarter)}}
** We have patches for this already! Not landed, but that's not our goal.

=== WebAPI ===
* {{miss|finalize moving main thread IDB to PBackground including blobs}} (bent)
** Lots of other things pulled bent away from this but it's progressing well when he has the time to work on it.
** This work is basically done, but did not land in time for end of Q2.
* {{miss|Convert DataStore cursors and DataStore object itself from JS to C++ (baku)}}
** DataStore Service didn't land until late in the quarter so not enough time to work on these other parts of DataStore by the end of Q2.
* {{miss|Finalize moving quotamanager to PBackground}} (janv)
** Jan took care of a bunch of the work leading up to this, but that took longer than expected.
* {{done|clarify design and spec issues around Fetch for Service Workers to ensure they're implementable}} (annevk)
** ServiceWorker work is not blocked on the Fetch spec at this point, and our implementation of Fetch is moving along.
* {{miss|implement gecko side of [http://w3c.github.io/manifest/ manifest] spec}} ({{bug|997779}}) (marcosc)
** Implement processing of V1 members (name, orientation, display, icons, start_url).
** This did not make it due to vacations and the lack of others' review bandwidth.
* {{risk|finish [https://w3c.github.io/screen-orientation/ device orientation] spec with Mounir}} (marcosc)
** Write tests for all conformance requirements.
** Publish LC by Monday, June 30.
** work has been done here and is waiting on the review of others and integration afterward

=== JS ===
* {{jrisk|941796}} Generational GC on Firefox OS [Scale FirefoxOS]

=== Accessibility ===
* {{miss|Sandboxing support: create and update cached structure of the accessible tree in the parent process (tbsaunde)}}
** This is in its second review already, so very close to done, just not landed.
* {{miss|Windows support: Land basic UIA text navigation implementation (surkov)}}
** About 40% completed.
* {{done|FFOS/GAIA: fix 9 [http://mzl.la/1g3rSJs P1 Gaia accessibility bugs] (there are 9 total at time of writing)}}
** Priorities may shift as there is flux and possible force multiplier work (e.g. web components).

=== Perf ===

* Improve Firefox responsiveness & startup time:
** Finish session-store work:
*** {{risk|Improve session-store startup time {{bug|987592}} }}
*** {{ok|Store less data in the sessionstore.js file {{bug|943352}} }}
*** {{ok|Break up janky operations into smaller chunks {{bug|984886}} }}
** Start eliminating top main-thread I/O offenders reported to Telemetry {{bug|572459}}:
*** 1. {{done|Remove main-thread IO from background update of {profile}\blocklist.xml {{bug|989419}} }}
*** 2. {{done|Avoid main-thread IO in Sync code {{bug|988301}} }}
*** 3. {{done|Avoid main-thread IO for {profile}\addons.json {{bug|988292}} }}
*** 4. {{done|Search service was falling back to synchronous initialization {{bug|785487}} }}
*** 5. {{done|User dictionary (persdict.dat) read on the main thread {{bug|880864}} }}
*** 6. {{done|Avoid main-thread IO for {profile}\blocklist.xml {{bug|988304}} }}
** {{ok|New storage system for prefs {{bug|897049}} }}
** {{done|The add-on compatibility dialog should not interrupt startup unless strictly necessary {{bug|760356}} }}
** {{ok|Investigate feasibility of starting Flash plugin instances asynchronously {{bug|998863}} }}

* Fill gaps in test coverage (vs press benchmarks) and prevent regressions:
** {{ok|Create a Talos test for "cold" startup time {{bug|936617}} }}
** {{done|Create a Talos test for time to restore a previous session {{bug|936630}} }}
** {{done|Integrate our new power-profiling test into the test infrastructure {{bug|962715}} }}
** {{ok|Automatically detect new sources of main-thread I/O in tests {{bug|998794}} }}
** {{done|Monitor & track regressions in important Talos tests during each release cycle}}

* Partner with other teams on projects with big perf impact
** {{ok|Assist Necko team with measuring performance of new network cache}}
** {{done|Make it easier to debug performance regressions by (optionally) capturing profiles during Talos tests {{bug|967619}} }}
** {{ok|Expand use of the T100 tablet/laptop as a reference slow device}}
** {{ok|Work with fx-team on ongoing regressions}}
** {{ok|Add performance tests for OMTC/APZC}}

* Study impact of extensions on Firefox performance
** {{ok|Create a Telemetry dashboard to expose add-ons' impact on Firefox startup time}}

* Grow community:
** {{ok|Mentor at least 5 new external contributors}}

=== Networking ===

* {{risk|Mitigate CSRF attacks against internal networks (block rfc 1918 local addresses from non-local addresses) ({{bug|354493}}) (sworkman) }}
** this is close enough that it may actually land today.
* {{done|HTTP/2: implement draft-11 of HTTP/2 spec and continue participating in spec development. (hurley / mcmanus) }}
* {{done|Turn on new HTTP cache in nightly (honza / michal) }}
* {{miss| NetworkLinkService should be enabled so Necko can respond to network changes ({{bug|939318}}) (bagder) }}
** subtle issues and feature creep. Should land in first half of next quarter (and we're doing a Q3 goal with followup work)
* {{miss|B2G: Provide way to "set network offline" per app ({{bug|786419}}) (valentin) }}
** We had to re-architect this now that apps can share a single B2G process. Patch in progress, should be done within a week or two.
* {{drop|Gather data and produce a report on performance wins vs resource costs of the seer on several desktop and mobile scenarios. (hurley) }}
** We've decided to re-name the seer the "network predictor" and to re-write it using the HTTP cache instead of SQLite, with Q3 target. So no performance numbers will be available this quarter.
* {{done|Download manager sometimes thinks that incomplete downloads are complete ({{bug|237623}}) }}

=== Mobile ===
=== A*Team ===
full list: [[Auto-tools/Goals/2014Q2]]

* B2G
** {{done|}} Deliver v2 of the FxOS Certification Suite
** {{miss|}} Build a common harness for Python and NodeJS Marionette tests, and enable them to run on devices and emulators
*** on-track for delivery in early Q3

* Performance
** {{done|}} Deploy a Talos dashboard that will allow Talos regressions to be more easily "sheriffed"
** {{done|}} Improve Eideticker's ability to scale
** {{done|}} Prototype Datazilla alerts for Talos and Eideticker data

* Mobile
** {{done|}} Move Android 2.3 reftests off of tegras
** {{done|}} Designate autophone and/or Eideticker as official perf systems for Android 2.3

* Bugzilla
** {{done|}} Migrate BMO and upstream Bugzilla CI from Tinderbox to travis-ci.
** {{done|}} Continue and deepen analysis of BMO perf data.
** {{done|}} Determine list of possible improvements, estimate gains, prioritize, and implement.

* Treeherder
** {{done|}} Deploy a production version of Treeherder in coordination with Laura's team
** {{miss|}} Define and implement a sheriff transition plan to move from TBPL to Treeherder
*** Production deployment took much longer than anticipated; sheriff transition to occur in first half of Q3
** {{done|}} Have Treeherder report data to OrangeFactor

* Community
** {{done|}} Refresh our list of "good first bugs" on a monthly basis
** {{done|}} Review these and make sure they have adequate information for contributors to start with
** {{done|}} Keep the numbers of open good first bugs steady or increasing

=== Web Engineering ===
* crash-stats
** {{done|}} Prototype work to support 100% crash processing for support classification and better user retention after a crash [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Implement symbol upload by partners [Scale FirefoxOS]
** {{done|}} Better search, graphs, and correlation reports to support QA and Crashkill teams [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Infrastructure improvements to support shipping engineer-requested features faster [Get Firefox on a Growth Trajectory / Scale FxOS]

* FHR
** {{done|}} Research and develop a plan for addressing sideloading [Invest in Sustainability]

* DXR
** {{miss|}} Move to a more scalable data store to enable indexing all trees [Scale FxOS]. Plugin API designed and implemented. 4 out of 5 plugins ported. ES query structure benched and proven. ES trigram-accelerated regex matching invented. To do: port indexing to ES, port clang plugin to ES, port filters to ES, port querying machinery to ES.
** {{drop|}} Implement search result mixing [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Improve documentation and install to lower the bar for contribution [Enable Communities with Impact] [http://dxr.readthedocs.org/en/latest/ Here it is.]

* l10n
** {{miss|}} (stretch) Remove dependency on buildbot (in progress, will carry to q3) [Enable Communities with Impact]

* Plugincheck
** {{done|}} Ship new version to support Firefox 29+ [Get Firefox on a Growth Trajectory]

* Air Mozilla
** {{done|}} Open event editing to all signed in users, wiki style [Enable Communities with Impact]
** {{done|}} Protoype ability to search by transcript [Enable Communities with Impact]

[https://etherpad.mozilla.org/webeng-q22014 Full list]

=== SUMO and Input ===
* SUMO
** {{drop|}} Implement interactive onboarding for new community volunteers [Enable communities with impact]
** {{done|}} Implement an initial community hub [Enable communities with impact]
** {{done|}} Prototype BuddyUp app: interactive support for FirefoxOS [Scale FirefoxOS]

* Input
** {{done|}} Integrate with Gengo translation API to improve localization [Scale FirefoxOS]
** {{done|}} (stretch) Implement and roll out new product-centric dashboards [Scale FirefoxOS]

[https://etherpad.mozilla.org/sumodev-2014-goals Full list]

=== Release Engineering ===
* {{ok|}} Plan and implement a sustainable approach to releases on legacy Android platforms [Get Firefox on a Growth Trajectory]
* {{done|}} Support infrastructure work on closing scl3 datacenter to save cost [Get Firefox on a Growth Trajectory]
* {{prev|}} Implement automation (slave loan tool) to reduce manual work [Get Firefox on a Growth Trajectory]
* {{ok|}} Stand up device builds for b2g reference phones [Scale FirefoxOS]
* {{done|}} Remove dependencies on and turn off deprecated systems [Get Firefox on a Growth Trajectory]
* {{done|}} Audit monitoring and instrumentation of release systems with a view to getting better insight, enabling better agility [Scale FirefoxOS]
* {{risk|}} Continue Balrog (new AUS) rollout to beta, and prepare for release/ESR [Get Firefox on a Growth Trajectory]
* {{ok|}} Automate merge day processes [Get Firefox on a Growth Trajectory]
* Continue infrastructure improvement program:
** {{ok|}} Move more work into the cloud to reduce cost and increase agility [Scale FirefoxOS]
** {{risk|}} Improve build and test environment for Windows [Get Firefox on a Growth Trajectory]
** {{risk|}} Get taskcluster ready to replace buildbot in Q3 and Q4 [Scale FirefoxOS]
* Joint goals with A-team:
** {{prev|}} Design an API that will be the single source of truth about release information [Get Firefox on a Growth Trajectory]

[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Ajlqy6z1WDBvdGNxaFFpbnQ4UDdySzZVcGU1RkN4b0E&usp=sharing&pli=1#gid=10 Full list]

=== Release Engineering Operations ===

* Datacenter Consolidation
** {{done| Migrate SCL1 infrastructure to SCL3 and close SCL1 datacenter. {{bug|981124}} and {{bug|961164}} [Datacenter consolidation and cost reduction] - completion date is July 14th }}
** {{done| Decommission deprecated hardware. {{bug|997213}} [Datacenter consolidation and cost reduction] }}

* Build/Test System Performance Enhancements
** {{done| Create a POC for Windows build systems on seamicro/SSD hardware and replicate to replace most of the existing Windows build infrastructure if successful. {{bug|982261}} [Get Firefox on a Growth Trajectory] }}
** {{drop| Create a POC for OS X build systems using SSD drives and replicate to the rest of the existing OS X build infrastructure if successful. {{bug|992364}} [Get Firefox on a Growth Trajectory] - build times did not expereince the expected time reduction }}
** {{drop| Architect and deploy a 3-node Ceph Prototype instance if tests on the existing POC show significant build speed increases. {{bug|995512}} [Get Firefox on a Growth Trajectory] - ceph did not prove appropriate for this use }}

* Build/Test System Self-Serve Re-architecture
** {{miss| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Growth Trajectory] - we expect this to be finished within the first few weeks of Q3 }}
** {{done| Develop a new image creation solution for 2008R2 build machines which can be used to deploy on bare metal. {{bug|798657}} [Get Firefox on a Growth Trajectory] }}

[https://etherpad.mozilla.org/relops-q22014 Full list]

=== Developer Services ===
* {{ok|}} Review and scale out git architecture [Scale FirefoxOS]
* {{ok|}} (with B-team) Improve performance and review tools for Bugzilla [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{done|}} (with A-team) Deploy better tree visualization tools [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{done|}} Plan and prototype future release engineering architecture [Get Firefox on a Growth Trajectory / Scale FirefoxOS]

[https://etherpad.mozilla.org/devservices-Q22014 Full list]

=== Security & Privacy ===
Full list here: [[SecurityEngineering/2014/Q2Goals]]

* Web Platform Security
** {{done|plan out replacement for nsIContentPolicy and start executing}} (dri=tanvi, +sicking,ckerschb)
** {{done|Make new CSP parser on by default in nightly}} (dri=ckerschb, +grobinson,sstamm)
** {{done|Land WebCrypto}} (dri=rbarnes) (tracking {{Bug|865789}})
* Secure Client Platform
** {{miss | (moved to blassey, working, pending review, eta ~ 2 weeks) Get open.h264 plugin sandboxed on windows}} [dri=sstamm, a=tabraldes]
** {{miss | (moved to blassey, working, pending review, eta ~ 2 weeks) sandboxing logging (warning mode or logging of violations on TBPL)}} [dri=bobowen, a=sstamm,tabraldes]
* Secure Communications
** {{done|Land key pinning}} [dri=cviecco, a=keeler,mmc]
** {{done|mozilla::pkix on by default, riding the train to 31}} [dri=keeler, a=cviecco]
** {{defer| BONUS: Deploy UI for cert error reporting}} [dri=grobinson]
* Tracking Protection / Privacy
** {{miss|Get through the [https://github.com/mozilla/lightbeam/issues/milestones next 2 releases] of Lightbeam}} (one done) [dri=mmc, a=grobinson]

=== Firefox and Platform Security ===
* {{miss|Create list of 3rd party code in Firefox with versions, upstream versions, and source locations}}
* {{done|Create fuzzer for WebNFC}}
* {{done|Create IndexedDB fuzzer}} (make langfuzz work for async web apis)
** Proof of concept created but not clear if it can be turned into real fuzzer.
* {{done|Fuzz JS on ODROID ARM hardware to find bugs masked in Simulator}}
* {{done|incorporate randomized build configs into JSFunFuzz harness}}
* {{done|Fuzz Workers and add fuzzing support for Shared Workers}}
* {{done|Create tool to auto-incorporate .webidl interfaces into DOM fuzzer}}
* {{done|Learn peach well well enough to create new pits. Test and document use of Peach on Linux}}
* {{ok|Work with various Firefox engineering teams to develop an alternative Firefox review process}}

=== Games Program ===

* Documentation
** {{done|Emscripten Documentation}}
*** Primary goal is to get a contractor, candidate identified, statement of work underway.
** {{ok|MDN General Documentation}}
*** Resources are attached, Chris Mills is driving it and games program groups are writing articles.
* {{ok|Partner approval of first B2G Emscripten Game Project}}
** Work week completed, graphics team has some fixes for 1.4 that appear low risk and provide 10fps we needed.
** Bug count is down to a handful after the week and we will be sending a Release Candidate to Disney as soon as the graphics fixes land.
* {{done|Train up replacement for Martin on Project Management related issues.}}
** Erin training is ongoing and she is already taking the lead on projects.
** No concerns of transitioning ownership of PM issue to her at this point.
* {{ok|QA}}
** Process is being worked out using the partner project
** Still need to improve general testing of game related features but expect to complete this once partner project is shipped.
* {{prev|Game Focus Benchmarking}}
** Project currently at risk as no resources are attached to the project.
** WebGL benchmarking is not currently automated and work is stalled.

Platform/2014-Q2-Goals

2014-07-01T17:06:31Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
Items marked [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 here] with release 31 and 32 are part of the Q2 landings.

=== Layout ===

* {{ok|Table Rendering with DisplayLists}}

* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Vertical text: Implement Layout frame migration to logical coordinates https://etherpad.mozilla.org/css-writing-modes
** {{done|convert cross-layout classes}}

* Text Performance bugs ( https://etherpad.mozilla.org/textperfworkitems )
** {{ok|large text frames / interruptible reflow}}
** {{ok|enumerated font list fixes}}

* Improve Restyling Performance
** {{ok|bug 931668}}
** {{bug|977991}}
** {{bug|804975}}, {{bug|977594}}

* GFx work items
** {{ok|E10S BasicCompositor}}
** {{ok|GFx tiling}}
** {{ok|Accelerated Filters}}
*** spec work
*** shader & support work

* CSS Flexbox
** {{done|pagination}}
** recently-finalized spec changes (abspos, min-width, flex sizing) (874718, 984711, 985304)

* Animations & Transitions
** {{miss|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{done|test_animations covering OMTA}}
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{miss|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|Spec an API for querying basic properties of running CSS animations/transitions}}

* Ship and/or unprefix:
** {{done|position:sticky}}
** {{done|Font-features that need fallback support (eg. small-caps)}}

* {{miss|3D Transforms}}
** interop bugs and spec improvement (bug 976365)
** implement preserve-3d proposal
** perf work

* {{miss|Font Inflation and Reflow-on-Zoom }}
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* CSS Projects with Adobe
** {{ok|CSS Filters}}
** {{ok|CSS Masking}}
** {{ok|CSS Compositing}}

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Fonts
** {{ok|font load events}}

=== Media ===
* {{miss|Pref on MSE/VP9 for Firefox 31}}
** Expecting to land in Firefox 32 (see below)
* {{miss|Pref on MSE/VP9 for Firefox 32}}
* {{miss|Enable MSE/MP4 on Windows for Firefox 32}}
** Expecting to land on 33

=== DOM ===
* {{done|Implement Xrays to 3 out of the following: Functions ({{bug|976148}}), Objects ({{bug|987111}}), Array/Array-like ({{bug|987163}}), and Error ({{bug|987669}})}}
* {{miss|Get rid of the long tail of C++ objects that are still exposed to the web using XPConnect}}
** We had less time for this than expected due to a previous quarter missed goal taking longer than expected to finish up (now done). Everything left on this list is already moving or planned, but will flow out into Q3.
* {{done|Get LeakSanitizer builds enabled by default ({{bug|988041}})}}
* {{done|Identify and fix (DOM stuff, at least) hotspots in b2g app startup (smaug)}}
* {{miss|refactor how tokenizer and tree builder use buffers to reduce memory pressure crashes (hsivonen)}}
** Henri has spent a lot of time with other responsibilities
* {{miss|Land all non-cache bits of Service Workers preffed-off (on is a bonus) on m-c (nsm)}}
** While this goal as written is a miss the overall progress towards Service Workers is progressing very well. This missed due to us not getting other resources on this quick enough due to other responsibilities, but velocity is really good now.
* {{done|Help guide and review requestAutocomplete backend implementation ({{bug|939351}})}} (likely smaug)
** The DOM team has been responsive to requests and implementation by the Firefox team is progressing.
* {{done|implement [http://picture.responsiveimages.org/ <picture>] ({{bug|870022}}) (johns)}}
** Things are looking good for landing here now that srcset is complete.
* {{miss|Ensure plugins are shippable for e10s}} (sort of {{bug|874016}}) (johns)
** John is working on this but <picture> took more of the quarter than expected.
* {{miss|Implement Shadow DOM :host style selector ({{bug|992245}})}} (wchen)
** wchen got caught up with other Web Components issues affecting gaia so this may not happen in Q2.
* {{done|Enable Shadow DOM for certified apps ({{bug|1000199}})}} (wchen)
* {{done|Define a plan for how to instrument code that triggers COW of pages post forking in a post Nuwa world (bonus if we can actually build that tool this quarter)}}
** We have patches for this already! Not landed, but that's not our goal.

=== WebAPI ===
* {{miss|finalize moving main thread IDB to PBackground including blobs}} (bent)
** Lots of other things pulled bent away from this but it's progressing well when he has the time to work on it.
** This work is basically done, but did not land in time for end of Q2.
* {{miss|Convert DataStore cursors and DataStore object itself from JS to C++ (baku)}}
** DataStore Service didn't land until late in the quarter so not enough time to work on these other parts of DataStore by the end of Q2.
* {{miss|Finalize moving quotamanager to PBackground}} (janv)
** Jan took care of a bunch of the work leading up to this, but that took longer than expected.
* {{done|clarify design and spec issues around Fetch for Service Workers to ensure they're implementable}} (annevk)
** ServiceWorker work is not blocked on the Fetch spec at this point, and our implementation of Fetch is moving along.
* {{miss|implement gecko side of [http://w3c.github.io/manifest/ manifest] spec}} ({{bug|997779}}) (marcosc)
** Implement processing of V1 members (name, orientation, display, icons, start_url).
** This did not make it due to vacations and the lack of others' review bandwidth.
* {{risk|finish [https://w3c.github.io/screen-orientation/ device orientation] spec with Mounir}} (marcosc)
** Write tests for all conformance requirements.
** Publish LC by Monday, June 30.
** work has been done here and is waiting on the review of others and integration afterward

=== JS ===
* {{jrisk|941796}} Generational GC on Firefox OS [Scale FirefoxOS]

=== Accessibility ===
* {{miss|Sandboxing support: create and update cached structure of the accessible tree in the parent process (tbsaunde)}}
** This is in its second review already, so very close to done, just not landed.
* {{miss|Windows support: Land basic UIA text navigation implementation (surkov)}}
** About 40% completed.
* {{done|FFOS/GAIA: fix 9 [http://mzl.la/1g3rSJs P1 Gaia accessibility bugs] (there are 9 total at time of writing)}}
** Priorities may shift as there is flux and possible force multiplier work (e.g. web components).

=== Perf ===

* Improve Firefox responsiveness & startup time:
** Finish session-store work:
*** {{risk|Improve session-store startup time {{bug|987592}} }}
*** {{ok|Store less data in the sessionstore.js file {{bug|943352}} }}
*** {{ok|Break up janky operations into smaller chunks {{bug|984886}} }}
** Start eliminating top main-thread I/O offenders reported to Telemetry {{bug|572459}}:
*** 1. {{done|Remove main-thread IO from background update of {profile}\blocklist.xml {{bug|989419}} }}
*** 2. {{done|Avoid main-thread IO in Sync code {{bug|988301}} }}
*** 3. {{done|Avoid main-thread IO for {profile}\addons.json {{bug|988292}} }}
*** 4. {{done|Search service was falling back to synchronous initialization {{bug|785487}} }}
*** 5. {{done|User dictionary (persdict.dat) read on the main thread {{bug|880864}} }}
*** 6. {{done|Avoid main-thread IO for {profile}\blocklist.xml {{bug|988304}} }}
** {{ok|New storage system for prefs {{bug|897049}} }}
** {{done|The add-on compatibility dialog should not interrupt startup unless strictly necessary {{bug|760356}} }}
** {{ok|Investigate feasibility of starting Flash plugin instances asynchronously {{bug|998863}} }}

* Fill gaps in test coverage (vs press benchmarks) and prevent regressions:
** {{ok|Create a Talos test for "cold" startup time {{bug|936617}} }}
** {{done|Create a Talos test for time to restore a previous session {{bug|936630}} }}
** {{done|Integrate our new power-profiling test into the test infrastructure {{bug|962715}} }}
** {{ok|Automatically detect new sources of main-thread I/O in tests {{bug|998794}} }}
** {{done|Monitor & track regressions in important Talos tests during each release cycle}}

* Partner with other teams on projects with big perf impact
** {{ok|Assist Necko team with measuring performance of new network cache}}
** {{done|Make it easier to debug performance regressions by (optionally) capturing profiles during Talos tests {{bug|967619}} }}
** {{ok|Expand use of the T100 tablet/laptop as a reference slow device}}
** {{ok|Work with fx-team on ongoing regressions}}
** {{ok|Add performance tests for OMTC/APZC}}

* Study impact of extensions on Firefox performance
** {{ok|Create a Telemetry dashboard to expose add-ons' impact on Firefox startup time}}

* Grow community:
** {{ok|Mentor at least 5 new external contributors}}

=== Networking ===

* {{risk|Mitigate CSRF attacks against internal networks (block rfc 1918 local addresses from non-local addresses) ({{bug|354493}}) (sworkman) }}
** this is close enough that it may actually land today.
* {{done|HTTP/2: implement draft-11 of HTTP/2 spec and continue participating in spec development. (hurley / mcmanus) }}
* {{done|Turn on new HTTP cache in nightly (honza / michal) }}
* {{miss| NetworkLinkService should be enabled so Necko can respond to network changes ({{bug|939318}}) (bagder) }}
** subtle issues and feature creep. Should land in first half of next quarter (and we're doing a Q3 goal with followup work)
* {{miss|B2G: Provide way to "set network offline" per app ({{bug|786419}}) (valentin) }}
** We had to re-architect this now that apps can share a single B2G process. Patch in progress, should be done within a week or two.
* {{drop|Gather data and produce a report on performance wins vs resource costs of the seer on several desktop and mobile scenarios. (hurley) }}
** We've decided to re-name the seer the "network predictor" and to re-write it using the HTTP cache instead of SQLite, with Q3 target. So no performance numbers will be available this quarter.
* {{done|Download manager sometimes thinks that incomplete downloads are complete ({{bug|237623}}) }}

=== Mobile ===
=== A*Team ===
full list: [[Auto-tools/Goals/2014Q2]]

* B2G
** {{done|}} Deliver v2 of the FxOS Certification Suite
** {{miss|}} Build a common harness for Python and NodeJS Marionette tests, and enable them to run on devices and emulators
*** on-track for delivery in early Q3

* Performance
** {{done|}} Deploy a Talos dashboard that will allow Talos regressions to be more easily "sheriffed"
** {{done|}} Improve Eideticker's ability to scale
** {{done|}} Prototype Datazilla alerts for Talos and Eideticker data

* Mobile
** {{done|}} Move Android 2.3 reftests off of tegras
** {{done|}} Designate autophone and/or Eideticker as official perf systems for Android 2.3

* Bugzilla
** {{done|}} Migrate BMO and upstream Bugzilla CI from Tinderbox to travis-ci.
** {{done|}} Continue and deepen analysis of BMO perf data.
** {{done|}} Determine list of possible improvements, estimate gains, prioritize, and implement.

* Treeherder
** {{done|}} Deploy a production version of Treeherder in coordination with Laura's team
** {{miss|}} Define and implement a sheriff transition plan to move from TBPL to Treeherder
*** Production deployment took much longer than anticipated; sheriff transition to occur in first half of Q3
** {{done|}} Have Treeherder report data to OrangeFactor

* Community
** {{done|}} Refresh our list of "good first bugs" on a monthly basis
** {{done|}} Review these and make sure they have adequate information for contributors to start with
** {{done|}} Keep the numbers of open good first bugs steady or increasing

=== Web Engineering ===
* crash-stats
** {{done|}} Prototype work to support 100% crash processing for support classification and better user retention after a crash [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Implement symbol upload by partners [Scale FirefoxOS]
** {{done|}} Better search, graphs, and correlation reports to support QA and Crashkill teams [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Infrastructure improvements to support shipping engineer-requested features faster [Get Firefox on a Growth Trajectory / Scale FxOS]

* FHR
** {{done|}} Research and develop a plan for addressing sideloading [Invest in Sustainability]

* DXR
** {{miss|}} Move to a more scalable data store to enable indexing all trees [Scale FxOS]. Plugin API designed and implemented. 4 out of 5 plugins ported. ES query structure benched and proven. ES trigram-accelerated regex matching invented. To do: port indexing to ES, port clang plugin to ES, port filters to ES, port querying machinery to ES.
** {{drop|}} Implement search result mixing [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Improve documentation and install to lower the bar for contribution [Enable Communities with Impact] [http://dxr.readthedocs.org/en/latest/ Here it is.]

* l10n
** {{miss|}} (stretch) Remove dependency on buildbot (in progress, will carry to q3) [Enable Communities with Impact]

* Plugincheck
** {{done|}} Ship new version to support Firefox 29+ [Get Firefox on a Growth Trajectory]

* Air Mozilla
** {{done|}} Open event editing to all signed in users, wiki style [Enable Communities with Impact]
** {{done|}} Protoype ability to search by transcript [Enable Communities with Impact]

[https://etherpad.mozilla.org/webeng-q22014 Full list]

=== SUMO and Input ===
* SUMO
** {{drop|}} Implement interactive onboarding for new community volunteers [Enable communities with impact]
** {{done|}} Implement an initial community hub [Enable communities with impact]
** {{done|}} Prototype BuddyUp app: interactive support for FirefoxOS [Scale FirefoxOS]

* Input
** {{done|}} Integrate with Gengo translation API to improve localization [Scale FirefoxOS]
** {{done|}} (stretch) Implement and roll out new product-centric dashboards [Scale FirefoxOS]

[https://etherpad.mozilla.org/sumodev-2014-goals Full list]

=== Release Engineering ===
* {{ok|}} Plan and implement a sustainable approach to releases on legacy Android platforms [Get Firefox on a Growth Trajectory]
* {{done|}} Support infrastructure work on closing scl3 datacenter to save cost [Get Firefox on a Growth Trajectory]
* {{prev|}} Implement automation (slave loan tool) to reduce manual work [Get Firefox on a Growth Trajectory]
* {{ok|}} Stand up device builds for b2g reference phones [Scale FirefoxOS]
* {{done|}} Remove dependencies on and turn off deprecated systems [Get Firefox on a Growth Trajectory]
* {{done|}} Audit monitoring and instrumentation of release systems with a view to getting better insight, enabling better agility [Scale FirefoxOS]
* {{risk|}} Continue Balrog (new AUS) rollout to beta, and prepare for release/ESR [Get Firefox on a Growth Trajectory]
* {{ok|}} Automate merge day processes [Get Firefox on a Growth Trajectory]
* Continue infrastructure improvement program:
** {{ok|}} Move more work into the cloud to reduce cost and increase agility [Scale FirefoxOS]
** {{risk|}} Improve build and test environment for Windows [Get Firefox on a Growth Trajectory]
** {{risk|}} Get taskcluster ready to replace buildbot in Q3 and Q4 [Scale FirefoxOS]
* Joint goals with A-team:
** {{prev|}} Design an API that will be the single source of truth about release information [Get Firefox on a Growth Trajectory]

[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Ajlqy6z1WDBvdGNxaFFpbnQ4UDdySzZVcGU1RkN4b0E&usp=sharing&pli=1#gid=10 Full list]

=== Release Engineering Operations ===

* Datacenter Consolidation
** {{done| Migrate SCL1 infrastructure to SCL3 and close SCL1 datacenter. {{bug|981124}} and {{bug|961164}} [Datacenter consolidation and cost reduction] - completion date is July 14th }}
** {{done| Decommission deprecated hardware. {{bug|997213}} [Datacenter consolidation and cost reduction] }}

* Build/Test System Performance Enhancements
** {{done| Create a POC for Windows build systems on seamicro/SSD hardware and replicate to replace most of the existing Windows build infrastructure if successful. {{bug|982261}} [Get Firefox on a Growth Trajectory] }}
** {{drop| Create a POC for OS X build systems using SSD drives and replicate to the rest of the existing OS X build infrastructure if successful. {{bug|992364}} [Get Firefox on a Growth Trajectory] - build times did not expereince the expected time reduction }}
** {{drop| Architect and deploy a 3-node Ceph Prototype instance if tests on the existing POC show significant build speed increases. {{bug|995512}} [Get Firefox on a Growth Trajectory] - ceph did not prove appropriate for this use }}

* Build/Test System Self-Serve Re-architecture
** {{missed| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Growth Trajectory] - we expect this to be finished within the first few weeks of Q3 }}
** {{done| Develop a new image creation solution for 2008R2 build machines which can be used to deploy on bare metal. {{bug|798657}} [Get Firefox on a Growth Trajectory] }}

[https://etherpad.mozilla.org/relops-q22014 Full list]

=== Developer Services ===
* {{ok|}} Review and scale out git architecture [Scale FirefoxOS]
* {{ok|}} (with B-team) Improve performance and review tools for Bugzilla [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{done|}} (with A-team) Deploy better tree visualization tools [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{done|}} Plan and prototype future release engineering architecture [Get Firefox on a Growth Trajectory / Scale FirefoxOS]

[https://etherpad.mozilla.org/devservices-Q22014 Full list]

=== Security & Privacy ===
Full list here: [[SecurityEngineering/2014/Q2Goals]]

* Web Platform Security
** {{done|plan out replacement for nsIContentPolicy and start executing}} (dri=tanvi, +sicking,ckerschb)
** {{done|Make new CSP parser on by default in nightly}} (dri=ckerschb, +grobinson,sstamm)
** {{done|Land WebCrypto}} (dri=rbarnes) (tracking {{Bug|865789}})
* Secure Client Platform
** {{miss | (moved to blassey, working, pending review, eta ~ 2 weeks) Get open.h264 plugin sandboxed on windows}} [dri=sstamm, a=tabraldes]
** {{miss | (moved to blassey, working, pending review, eta ~ 2 weeks) sandboxing logging (warning mode or logging of violations on TBPL)}} [dri=bobowen, a=sstamm,tabraldes]
* Secure Communications
** {{done|Land key pinning}} [dri=cviecco, a=keeler,mmc]
** {{done|mozilla::pkix on by default, riding the train to 31}} [dri=keeler, a=cviecco]
** {{defer| BONUS: Deploy UI for cert error reporting}} [dri=grobinson]
* Tracking Protection / Privacy
** {{miss|Get through the [https://github.com/mozilla/lightbeam/issues/milestones next 2 releases] of Lightbeam}} (one done) [dri=mmc, a=grobinson]

=== Firefox and Platform Security ===
* {{miss|Create list of 3rd party code in Firefox with versions, upstream versions, and source locations}}
* {{done|Create fuzzer for WebNFC}}
* {{done|Create IndexedDB fuzzer}} (make langfuzz work for async web apis)
** Proof of concept created but not clear if it can be turned into real fuzzer.
* {{done|Fuzz JS on ODROID ARM hardware to find bugs masked in Simulator}}
* {{done|incorporate randomized build configs into JSFunFuzz harness}}
* {{done|Fuzz Workers and add fuzzing support for Shared Workers}}
* {{done|Create tool to auto-incorporate .webidl interfaces into DOM fuzzer}}
* {{done|Learn peach well well enough to create new pits. Test and document use of Peach on Linux}}
* {{ok|Work with various Firefox engineering teams to develop an alternative Firefox review process}}

=== Games Program ===

* Documentation
** {{done|Emscripten Documentation}}
*** Primary goal is to get a contractor, candidate identified, statement of work underway.
** {{ok|MDN General Documentation}}
*** Resources are attached, Chris Mills is driving it and games program groups are writing articles.
* {{ok|Partner approval of first B2G Emscripten Game Project}}
** Work week completed, graphics team has some fixes for 1.4 that appear low risk and provide 10fps we needed.
** Bug count is down to a handful after the week and we will be sending a Release Candidate to Disney as soon as the graphics fixes land.
* {{done|Train up replacement for Martin on Project Management related issues.}}
** Erin training is ongoing and she is already taking the lead on projects.
** No concerns of transitioning ownership of PM issue to her at this point.
* {{ok|QA}}
** Process is being worked out using the partner project
** Still need to improve general testing of game related features but expect to complete this once partner project is shipped.
* {{prev|Game Focus Benchmarking}}
** Project currently at risk as no resources are attached to the project.
** WebGL benchmarking is not currently automated and work is stalled.

Platform/2014-Q2-Goals

2014-07-01T15:08:53Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
Items marked [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 here] with release 31 and 32 are part of the Q2 landings.

=== Layout ===

* {{ok|Table Rendering with DisplayLists}}

* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Vertical text: Implement Layout frame migration to logical coordinates https://etherpad.mozilla.org/css-writing-modes
** {{done|convert cross-layout classes}}

* Text Performance bugs ( https://etherpad.mozilla.org/textperfworkitems )
** {{ok|large text frames / interruptible reflow}}
** {{ok|enumerated font list fixes}}

* Improve Restyling Performance
** {{ok|bug 931668}}
** {{bug|977991}}
** {{bug|804975}}, {{bug|977594}}

* GFx work items
** {{ok|E10S BasicCompositor}}
** {{ok|GFx tiling}}
** {{ok|Accelerated Filters}}
*** spec work
*** shader & support work

* CSS Flexbox
** {{done|pagination}}
** recently-finalized spec changes (abspos, min-width, flex sizing) (874718, 984711, 985304)

* Animations & Transitions
** {{miss|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{done|test_animations covering OMTA}}
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{miss|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|Spec an API for querying basic properties of running CSS animations/transitions}}

* Ship and/or unprefix:
** {{done|position:sticky}}
** {{done|Font-features that need fallback support (eg. small-caps)}}

* {{miss|3D Transforms}}
** interop bugs and spec improvement (bug 976365)
** implement preserve-3d proposal
** perf work

* {{miss|Font Inflation and Reflow-on-Zoom }}
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* CSS Projects with Adobe
** {{ok|CSS Filters}}
** {{ok|CSS Masking}}
** {{ok|CSS Compositing}}

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Fonts
** {{ok|font load events}}

=== Media ===
* {{miss|Pref on MSE/VP9 for Firefox 31}}
** Expecting to land in Firefox 32 (see below)
* {{miss|Pref on MSE/VP9 for Firefox 32}}
* {{miss|Enable MSE/MP4 on Windows for Firefox 32}}
** Expecting to land on 33

=== DOM ===
* {{done|Implement Xrays to 3 out of the following: Functions ({{bug|976148}}), Objects ({{bug|987111}}), Array/Array-like ({{bug|987163}}), and Error ({{bug|987669}})}}
* {{miss|Get rid of the long tail of C++ objects that are still exposed to the web using XPConnect}}
** We had less time for this than expected due to a previous quarter missed goal taking longer than expected to finish up (now done). Everything left on this list is already moving or planned, but will flow out into Q3.
* {{done|Get LeakSanitizer builds enabled by default ({{bug|988041}})}}
* {{done|Identify and fix (DOM stuff, at least) hotspots in b2g app startup (smaug)}}
* {{miss|refactor how tokenizer and tree builder use buffers to reduce memory pressure crashes (hsivonen)}}
** Henri has spent a lot of time with other responsibilities
* {{miss|Land all non-cache bits of Service Workers preffed-off (on is a bonus) on m-c (nsm)}}
** While this goal as written is a miss the overall progress towards Service Workers is progressing very well. This missed due to us not getting other resources on this quick enough due to other responsibilities, but velocity is really good now.
* {{done|Help guide and review requestAutocomplete backend implementation ({{bug|939351}})}} (likely smaug)
** The DOM team has been responsive to requests and implementation by the Firefox team is progressing.
* {{done|implement [http://picture.responsiveimages.org/ <picture>] ({{bug|870022}}) (johns)}}
** Things are looking good for landing here now that srcset is complete.
* {{miss|Ensure plugins are shippable for e10s}} (sort of {{bug|874016}}) (johns)
** John is working on this but <picture> took more of the quarter than expected.
* {{miss|Implement Shadow DOM :host style selector ({{bug|992245}})}} (wchen)
** wchen got caught up with other Web Components issues affecting gaia so this may not happen in Q2.
* {{done|Enable Shadow DOM for certified apps ({{bug|1000199}})}} (wchen)
* {{done|Define a plan for how to instrument code that triggers COW of pages post forking in a post Nuwa world (bonus if we can actually build that tool this quarter)}}
** We have patches for this already! Not landed, but that's not our goal.

=== WebAPI ===
* {{miss|finalize moving main thread IDB to PBackground including blobs}} (bent)
** Lots of other things pulled bent away from this but it's progressing well when he has the time to work on it.
** This work is basically done, but did not land in time for end of Q2.
* {{miss|Convert DataStore cursors and DataStore object itself from JS to C++ (baku)}}
** DataStore Service didn't land until late in the quarter so not enough time to work on these other parts of DataStore by the end of Q2.
* {{miss|Finalize moving quotamanager to PBackground}} (janv)
** Jan took care of a bunch of the work leading up to this, but that took longer than expected.
* {{done|clarify design and spec issues around Fetch for Service Workers to ensure they're implementable}} (annevk)
** ServiceWorker work is not blocked on the Fetch spec at this point, and our implementation of Fetch is moving along.
* {{miss|implement gecko side of [http://w3c.github.io/manifest/ manifest] spec}} ({{bug|997779}}) (marcosc)
** Implement processing of V1 members (name, orientation, display, icons, start_url).
** This did not make it due to vacations and the lack of others' review bandwidth.
* {{risk|finish [https://w3c.github.io/screen-orientation/ device orientation] spec with Mounir}} (marcosc)
** Write tests for all conformance requirements.
** Publish LC by Monday, June 30.
** work has been done here and is waiting on the review of others and integration afterward

=== JS ===
* {{jrisk|941796}} Generational GC on Firefox OS [Scale FirefoxOS]

=== Accessibility ===
* {{miss|Sandboxing support: create and update cached structure of the accessible tree in the parent process (tbsaunde)}}
** This is in its second review already, so very close to done, just not landed.
* {{miss|Windows support: Land basic UIA text navigation implementation (surkov)}}
** About 40% completed.
* {{done|FFOS/GAIA: fix 9 [http://mzl.la/1g3rSJs P1 Gaia accessibility bugs] (there are 9 total at time of writing)}}
** Priorities may shift as there is flux and possible force multiplier work (e.g. web components).

=== Perf ===

* Improve Firefox responsiveness & startup time:
** Finish session-store work:
*** {{risk|Improve session-store startup time {{bug|987592}} }}
*** {{ok|Store less data in the sessionstore.js file {{bug|943352}} }}
*** {{ok|Break up janky operations into smaller chunks {{bug|984886}} }}
** Start eliminating top main-thread I/O offenders reported to Telemetry {{bug|572459}}:
*** 1. {{done|Remove main-thread IO from background update of {profile}\blocklist.xml {{bug|989419}} }}
*** 2. {{done|Avoid main-thread IO in Sync code {{bug|988301}} }}
*** 3. {{done|Avoid main-thread IO for {profile}\addons.json {{bug|988292}} }}
*** 4. {{done|Search service was falling back to synchronous initialization {{bug|785487}} }}
*** 5. {{done|User dictionary (persdict.dat) read on the main thread {{bug|880864}} }}
*** 6. {{done|Avoid main-thread IO for {profile}\blocklist.xml {{bug|988304}} }}
** {{ok|New storage system for prefs {{bug|897049}} }}
** {{done|The add-on compatibility dialog should not interrupt startup unless strictly necessary {{bug|760356}} }}
** {{ok|Investigate feasibility of starting Flash plugin instances asynchronously {{bug|998863}} }}

* Fill gaps in test coverage (vs press benchmarks) and prevent regressions:
** {{ok|Create a Talos test for "cold" startup time {{bug|936617}} }}
** {{done|Create a Talos test for time to restore a previous session {{bug|936630}} }}
** {{done|Integrate our new power-profiling test into the test infrastructure {{bug|962715}} }}
** {{ok|Automatically detect new sources of main-thread I/O in tests {{bug|998794}} }}
** {{done|Monitor & track regressions in important Talos tests during each release cycle}}

* Partner with other teams on projects with big perf impact
** {{ok|Assist Necko team with measuring performance of new network cache}}
** {{done|Make it easier to debug performance regressions by (optionally) capturing profiles during Talos tests {{bug|967619}} }}
** {{ok|Expand use of the T100 tablet/laptop as a reference slow device}}
** {{ok|Work with fx-team on ongoing regressions}}
** {{ok|Add performance tests for OMTC/APZC}}

* Study impact of extensions on Firefox performance
** {{ok|Create a Telemetry dashboard to expose add-ons' impact on Firefox startup time}}

* Grow community:
** {{ok|Mentor at least 5 new external contributors}}

=== Networking ===

* {{risk|Mitigate CSRF attacks against internal networks (block rfc 1918 local addresses from non-local addresses) ({{bug|354493}}) (sworkman) }}
** this is close enough that it may actually land today.
* {{done|HTTP/2: implement draft-11 of HTTP/2 spec and continue participating in spec development. (hurley / mcmanus) }}
* {{done|Turn on new HTTP cache in nightly (honza / michal) }}
* {{miss| NetworkLinkService should be enabled so Necko can respond to network changes ({{bug|939318}}) (bagder) }}
** subtle issues and feature creep. Should land in first half of next quarter (and we're doing a Q3 goal with followup work)
* {{miss|B2G: Provide way to "set network offline" per app ({{bug|786419}}) (valentin) }}
** We had to re-architect this now that apps can share a single B2G process. Patch in progress, should be done within a week or two.
* {{drop|Gather data and produce a report on performance wins vs resource costs of the seer on several desktop and mobile scenarios. (hurley) }}
** We've decided to re-name the seer the "network predictor" and to re-write it using the HTTP cache instead of SQLite, with Q3 target. So no performance numbers will be available this quarter.
* {{done|Download manager sometimes thinks that incomplete downloads are complete ({{bug|237623}}) }}

=== Mobile ===
=== A*Team ===
full list: [[Auto-tools/Goals/2014Q2]]

* B2G
** {{done|}} Deliver v2 of the FxOS Certification Suite
** {{miss|}} Build a common harness for Python and NodeJS Marionette tests, and enable them to run on devices and emulators
*** on-track for delivery in early Q3

* Performance
** {{done|}} Deploy a Talos dashboard that will allow Talos regressions to be more easily "sheriffed"
** {{done|}} Improve Eideticker's ability to scale
** {{done|}} Prototype Datazilla alerts for Talos and Eideticker data

* Mobile
** {{done|}} Move Android 2.3 reftests off of tegras
** {{done|}} Designate autophone and/or Eideticker as official perf systems for Android 2.3

* Bugzilla
** {{done|}} Migrate BMO and upstream Bugzilla CI from Tinderbox to travis-ci.
** {{done|}} Continue and deepen analysis of BMO perf data.
** {{done|}} Determine list of possible improvements, estimate gains, prioritize, and implement.

* Treeherder
** {{done|}} Deploy a production version of Treeherder in coordination with Laura's team
** {{miss|}} Define and implement a sheriff transition plan to move from TBPL to Treeherder
*** Production deployment took much longer than anticipated; sheriff transition to occur in first half of Q3
** {{done|}} Have Treeherder report data to OrangeFactor

* Community
** {{done|}} Refresh our list of "good first bugs" on a monthly basis
** {{done|}} Review these and make sure they have adequate information for contributors to start with
** {{done|}} Keep the numbers of open good first bugs steady or increasing

=== Web Engineering ===
* crash-stats
** {{done|}} Prototype work to support 100% crash processing for support classification and better user retention after a crash [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Implement symbol upload by partners [Scale FirefoxOS]
** {{done|}} Better search, graphs, and correlation reports to support QA and Crashkill teams [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Infrastructure improvements to support shipping engineer-requested features faster [Get Firefox on a Growth Trajectory / Scale FxOS]

* FHR
** {{done|}} Research and develop a plan for addressing sideloading [Invest in Sustainability]

* DXR
** {{miss|}} Move to a more scalable data store to enable indexing all trees [Scale FxOS]. Plugin API designed and implemented. 4 out of 5 plugins ported. ES query structure benched and proven. ES trigram-accelerated regex matching invented. To do: port indexing to ES, port clang plugin to ES, port filters to ES, port querying machinery to ES.
** {{drop|}} Implement search result mixing [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Improve documentation and install to lower the bar for contribution [Enable Communities with Impact] [http://dxr.readthedocs.org/en/latest/ Here it is.]

* l10n
** {{miss|}} (stretch) Remove dependency on buildbot (in progress, will carry to q3) [Enable Communities with Impact]

* Plugincheck
** {{done|}} Ship new version to support Firefox 29+ [Get Firefox on a Growth Trajectory]

* Air Mozilla
** {{done|}} Open event editing to all signed in users, wiki style [Enable Communities with Impact]
** {{done|}} Protoype ability to search by transcript [Enable Communities with Impact]

[https://etherpad.mozilla.org/webeng-q22014 Full list]

=== SUMO and Input ===
* SUMO
** {{drop|}} Implement interactive onboarding for new community volunteers [Enable communities with impact]
** {{done|}} Implement an initial community hub [Enable communities with impact]
** {{done|}} Prototype BuddyUp app: interactive support for FirefoxOS [Scale FirefoxOS]

* Input
** {{done|}} Integrate with Gengo translation API to improve localization [Scale FirefoxOS]
** {{done|}} (stretch) Implement and roll out new product-centric dashboards [Scale FirefoxOS]

[https://etherpad.mozilla.org/sumodev-2014-goals Full list]

=== Release Engineering ===
* {{ok|}} Plan and implement a sustainable approach to releases on legacy Android platforms [Get Firefox on a Growth Trajectory]
* {{done|}} Support infrastructure work on closing scl3 datacenter to save cost [Get Firefox on a Growth Trajectory]
* {{prev|}} Implement automation (slave loan tool) to reduce manual work [Get Firefox on a Growth Trajectory]
* {{ok|}} Stand up device builds for b2g reference phones [Scale FirefoxOS]
* {{done|}} Remove dependencies on and turn off deprecated systems [Get Firefox on a Growth Trajectory]
* {{done|}} Audit monitoring and instrumentation of release systems with a view to getting better insight, enabling better agility [Scale FirefoxOS]
* {{risk|}} Continue Balrog (new AUS) rollout to beta, and prepare for release/ESR [Get Firefox on a Growth Trajectory]
* {{ok|}} Automate merge day processes [Get Firefox on a Growth Trajectory]
* Continue infrastructure improvement program:
** {{ok|}} Move more work into the cloud to reduce cost and increase agility [Scale FirefoxOS]
** {{risk|}} Improve build and test environment for Windows [Get Firefox on a Growth Trajectory]
** {{risk|}} Get taskcluster ready to replace buildbot in Q3 and Q4 [Scale FirefoxOS]
* Joint goals with A-team:
** {{prev|}} Design an API that will be the single source of truth about release information [Get Firefox on a Growth Trajectory]

[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Ajlqy6z1WDBvdGNxaFFpbnQ4UDdySzZVcGU1RkN4b0E&usp=sharing&pli=1#gid=10 Full list]

=== Release Engineering Operations ===

* Datacenter Consolidation
** {{done| Migrate SCL1 infrastructure to SCL3 and close SCL1 datacenter. {{bug|981124}} and {{bug|961164}} [Datacenter consolidation and cost reduction] - completion date is July 14th }}
** {{done| Decommission deprecated hardware. {{bug|997213}} [Datacenter consolidation and cost reduction] }}

* Build/Test System Performance Enhancements
** {{done| Create a POC for Windows build systems on seamicro/SSD hardware and replicate to replace most of the existing Windows build infrastructure if successful. {{bug|982261}} [Get Firefox on a Growth Trajectory] }}
** {{drop| Create a POC for OS X build systems using SSD drives and replicate to the rest of the existing OS X build infrastructure if successful. {{bug|992364}} [Get Firefox on a Growth Trajectory] - build times did not expereince the expected time reduction }}
** {{drop| Architect and deploy a 3-node Ceph Prototype instance if tests on the existing POC show significant build speed increases. {{bug|995512}} [Get Firefox on a Growth Trajectory] - ceph did not prove appropriate for this use }}

* Build/Test System Self-Serve Re-architecture
** {{ok| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Growth Trajectory] }}
** {{ok| Develop a new image creation solution for 2008R2 build machines which can be used to deploy on bare metal. {{bug|798657}} [Get Firefox on a Growth Trajectory] }}

[https://etherpad.mozilla.org/relops-q22014 Full list]

=== Developer Services ===
* {{ok|}} Review and scale out git architecture [Scale FirefoxOS]
* {{ok|}} (with B-team) Improve performance and review tools for Bugzilla [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{done|}} (with A-team) Deploy better tree visualization tools [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{done|}} Plan and prototype future release engineering architecture [Get Firefox on a Growth Trajectory / Scale FirefoxOS]

[https://etherpad.mozilla.org/devservices-Q22014 Full list]

=== Security & Privacy ===
Full list here: [[SecurityEngineering/2014/Q2Goals]]

* Web Platform Security
** {{done|plan out replacement for nsIContentPolicy and start executing}} (dri=tanvi, +sicking,ckerschb)
** {{done|Make new CSP parser on by default in nightly}} (dri=ckerschb, +grobinson,sstamm)
** {{done|Land WebCrypto}} (dri=rbarnes) (tracking {{Bug|865789}})
* Secure Client Platform
** {{miss | (moved to blassey, working, pending review, eta ~ 2 weeks) Get open.h264 plugin sandboxed on windows}} [dri=sstamm, a=tabraldes]
** {{miss | (moved to blassey, working, pending review, eta ~ 2 weeks) sandboxing logging (warning mode or logging of violations on TBPL)}} [dri=bobowen, a=sstamm,tabraldes]
* Secure Communications
** {{done|Land key pinning}} [dri=cviecco, a=keeler,mmc]
** {{done|mozilla::pkix on by default, riding the train to 31}} [dri=keeler, a=cviecco]
** {{defer| BONUS: Deploy UI for cert error reporting}} [dri=grobinson]
* Tracking Protection / Privacy
** {{miss|Get through the [https://github.com/mozilla/lightbeam/issues/milestones next 2 releases] of Lightbeam}} (one done) [dri=mmc, a=grobinson]

=== Firefox and Platform Security ===
* {{miss|Create list of 3rd party code in Firefox with versions, upstream versions, and source locations}}
* {{done|Create fuzzer for WebNFC}}
* {{done|Create IndexedDB fuzzer}} (make langfuzz work for async web apis)
** Proof of concept created but not clear if it can be turned into real fuzzer.
* {{done|Fuzz JS on ODROID ARM hardware to find bugs masked in Simulator}}
* {{done|incorporate randomized build configs into JSFunFuzz harness}}
* {{done|Fuzz Workers and add fuzzing support for Shared Workers}}
* {{done|Create tool to auto-incorporate .webidl interfaces into DOM fuzzer}}
* {{done|Learn peach well well enough to create new pits. Test and document use of Peach on Linux}}
* {{ok|Work with various Firefox engineering teams to develop an alternative Firefox review process}}

=== Games Program ===

* Documentation
** {{done|Emscripten Documentation}}
*** Primary goal is to get a contractor, candidate identified, statement of work underway.
** {{ok|MDN General Documentation}}
*** Resources are attached, Chris Mills is driving it and games program groups are writing articles.
* {{ok|Partner approval of first B2G Emscripten Game Project}}
** Work week completed, graphics team has some fixes for 1.4 that appear low risk and provide 10fps we needed.
** Bug count is down to a handful after the week and we will be sending a Release Candidate to Disney as soon as the graphics fixes land.
* {{done|Train up replacement for Martin on Project Management related issues.}}
** Erin training is ongoing and she is already taking the lead on projects.
** No concerns of transitioning ownership of PM issue to her at this point.
* {{ok|QA}}
** Process is being worked out using the partner project
** Still need to improve general testing of game related features but expect to complete this once partner project is shipped.
* {{prev|Game Focus Benchmarking}}
** Project currently at risk as no resources are attached to the project.
** WebGL benchmarking is not currently automated and work is stalled.

Platform/2014-Q2-Goals

2014-06-26T09:26:06Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
Items marked [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 here] with release 31 and 32 are part of the Q2 landings.

=== Layout ===

* {{ok|Table Rendering with DisplayLists}}

* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Vertical text: Implement Layout frame migration to logical coordinates https://etherpad.mozilla.org/css-writing-modes
** {{ok|convert cross-layout classes}}

* Text Performance bugs ( https://etherpad.mozilla.org/textperfworkitems )
** {{ok|large text frames / interruptible reflow}}
** {{ok|enumerated font list fixes}}

* Improve Restyling Performance
** {{ok|bug 931668}}
** {{bug|977991}}
** {{bug|804975}}, {{bug|977594}}

* GFx work items
** {{ok|E10S BasicCompositor}}
** {{ok|GFx tiling}}
** {{ok|Accelerated Filters}}
*** spec work
*** shader & support work

* CSS Flexbox
** {{ok|pagination}}
** recently-finalized spec changes (abspos, min-width, flex sizing) (874718, 984711, 985304)

* Animations & Transitions
** {{ok|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{ok|test_animations covering OMTA}}
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{ok|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|Spec an API for querying basic properties of running CSS animations/transitions}}

* Ship and/or unprefix:
** {{done|position:sticky}}
** {{ok|Font-features that need fallback support (eg. small-caps)}}

* 3D Transforms
** interop bugs and spec improvement (bug 976365)
** implement preserve-3d proposal
** perf work

* Font Inflation and Reflow-on-Zoom
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* CSS Projects with Adobe
** {{ok|CSS Filters}}
** {{ok|CSS Masking}}
** {{ok|CSS Compositing}}

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Fonts
** {{ok|font load events}}

=== Media ===
* {{miss|Pref on MSE/VP9 for Firefox 31}}
** Expecting to land in Firefox 32 (see below)
* {{ok|Pref on MSE/VP9 for Firefox 32}}
* {{miss|Enable MSE/MP4 on Windows for Firefox 32}}
** Expecting to land on 33

=== DOM ===
* {{done|Implement Xrays to 3 out of the following: Functions ({{bug|976148}}), Objects ({{bug|987111}}), Array/Array-like ({{bug|987163}}), and Error ({{bug|987669}})}}
* {{risk|Get rid of the long tail of C++ objects that are still exposed to the web using XPConnect}}
** We had less time for this than expected due to a previous quarter missed goal taking longer than expected to finish up (now done). Lots of pieces moving here already though.
* {{ok|Get LeakSanitizer builds enabled by default ({{bug|988041}})}}
* {{done|Identify and fix (DOM stuff, at least) hotspots in b2g app startup (smaug)}}
* {{risk|refactor how tokenizer and tree builder use buffers to reduce memory pressure crashes (hsivonen)}}
** Henri has spent a lot of time with other responsibilities
* {{risk|Land all non-cache bits of Service Workers preffed-off (on is a bonus) on m-c (nsm)}}
** we're doing well here but we only have a few weeks left in Q2 and lots of reviews need to happen. Some in-person reviews the last week of June will help.
* {{ok|Help guide and review requestAutocomplete backend implementation ({{bug|939351}})}} (likely smaug)
** The DOM team has been responsive to requests and implementation by the Firefox team is progressing.
* {{prev|implement [http://picture.responsiveimages.org/ <picture>] ({{bug|870022}}) (johns)}}
** Things are looking good for landing here now that srcset is complete.
* {{risk|Ensure plugins are shippable for e10s}} (sort of {{bug|874016}}) (johns)
** John is working on this but <picture> took more of the quarter than expected.
* {{risk|Implement Shadow DOM :host style selector ({{bug|992245}})}} (wchen)
** wchen got caught up with other Web Components issues affecting gaia so this may not happen in Q2.
* {{done|Enable Shadow DOM for certified apps ({{bug|1000199}})}} (wchen)
* {{done|Define a plan for how to instrument code that triggers COW of pages post forking in a post Nuwa world (bonus if we can actually build that tool this quarter)}}
** We have patches for this already! Not landed, but that's not our goal.

=== WebAPI ===
* {{ok|finalize moving main thread IDB to PBackground including blobs}} (bent)
** Lots of other things pulled bent away from this but it's progressing well when he has the time to work on it.
* {{risk|Convert DataStore cursors and DataStore object itself from JS to C++ (baku)}}
** DataStore Service didn't land until late in the quarter so these other parts of DataStore are at risk for landing by the end of June.
* {{risk|Finalize moving quotamanager to PBackground}} (janv)
** Jan took care of a few other pieces of the move to PBackground and once FileHandle changes land, this can happen; unlikely for the end of June.
* {{ok|clarify design and spec issues around Fetch for Service Workers to ensure they're implementable}} (annevk)
** Good progress is being made here.
* {{risk|implement gecko side of [http://w3c.github.io/manifest/ manifest] spec}} ({{bug|997779}}) (marcosc)
** Implement processing of V1 members (name, orientation, display, icons, start_url).
** Finish implementation by Monday, June 30.
** This is waiting on reviews and with vacation, is at risk for happening by the end of June.
* {{risk|finish [https://w3c.github.io/screen-orientation/ device orientation] spec with Mounir}} (marcosc)
** Write tests for all conformance requirements.
** Publish LC by Monday, June 30.
** work has been done here and is waiting on the review of others and integration afterward

=== JS ===
* {{jrisk|941796}} Generational GC on Firefox OS [Scale FirefoxOS]

=== Accessibility ===
* {{ok|Sandboxing support: create and update cached structure of the accessible tree in the parent process (tbsaunde)}}
* {{risk|Windows support: Land basic UIA text navigation implementation (surkov)}}
* {{ok|FFOS/GAIA: fix 9 [http://mzl.la/1g3rSJs P1 Gaia accessibility bugs] (there are 9 total at time of writing)}}
** Priorities may shift as there is flux and possible force multiplier work (e.g. web components).

=== Perf ===

* Improve Firefox responsiveness & startup time:
** Finish session-store work:
*** {{risk|Improve session-store startup time {{bug|987592}} }}
*** {{ok|Store less data in the sessionstore.js file {{bug|943352}} }}
*** {{ok|Break up janky operations into smaller chunks {{bug|984886}} }}
** Start eliminating top main-thread I/O offenders reported to Telemetry {{bug|572459}}:
*** 1. {{done|Remove main-thread IO from background update of {profile}\blocklist.xml {{bug|989419}} }}
*** 2. {{done|Avoid main-thread IO in Sync code {{bug|988301}} }}
*** 3. {{done|Avoid main-thread IO for {profile}\addons.json {{bug|988292}} }}
*** 4. {{done|Search service was falling back to synchronous initialization {{bug|785487}} }}
*** 5. {{done|User dictionary (persdict.dat) read on the main thread {{bug|880864}} }}
*** 6. {{done|Avoid main-thread IO for {profile}\blocklist.xml {{bug|988304}} }}
** {{ok|New storage system for prefs {{bug|897049}} }}
** {{done|The add-on compatibility dialog should not interrupt startup unless strictly necessary {{bug|760356}} }}
** {{ok|Investigate feasibility of starting Flash plugin instances asynchronously {{bug|998863}} }}

* Fill gaps in test coverage (vs press benchmarks) and prevent regressions:
** {{ok|Create a Talos test for "cold" startup time {{bug|936617}} }}
** {{done|Create a Talos test for time to restore a previous session {{bug|936630}} }}
** {{done|Integrate our new power-profiling test into the test infrastructure {{bug|962715}} }}
** {{ok|Automatically detect new sources of main-thread I/O in tests {{bug|998794}} }}
** {{done|Monitor & track regressions in important Talos tests during each release cycle}}

* Partner with other teams on projects with big perf impact
** {{ok|Assist Necko team with measuring performance of new network cache}}
** {{done|Make it easier to debug performance regressions by (optionally) capturing profiles during Talos tests {{bug|967619}} }}
** {{ok|Expand use of the T100 tablet/laptop as a reference slow device}}
** {{ok|Work with fx-team on ongoing regressions}}
** {{ok|Add performance tests for OMTC/APZC}}

* Study impact of extensions on Firefox performance
** {{ok|Create a Telemetry dashboard to expose add-ons' impact on Firefox startup time}}

* Grow community:
** {{ok|Mentor at least 5 new external contributors}}

=== Networking ===

* {{ok|Mitigate CSRF attacks against internal networks (block rfc 1918 local addresses from non-local addresses) ({{bug|354493}}) (sworkman) }}
* {{done|HTTP/2: implement draft-11 of HTTP/2 spec and continue participating in spec development. (hurley / mcmanus) }}
* {{done|Turn on new HTTP cache in nightly (honza / michal) }}
* {{ok| NetworkLinkService should be enabled so Necko can respond to network changes ({{bug|939318}}) (bagder) }}
* {{ok|B2G: Provide way to "set network offline" per app ({{bug|786419}}) (valentin) }}
* {{drop|Gather data and produce a report on performance wins vs resource costs of the seer on several desktop and mobile scenarios. (hurley) }}
** We've decided to re-name the seer the "network predictor" and to re-write it using the HTTP cache instead of SQLite, with Q3 target. So no performance numbers will be available this quarter.

=== Mobile ===
=== A*Team ===
full list: [[Auto-tools/Goals/2014Q2]]

* B2G
** {{done|}} Deliver v2 of the FxOS Certification Suite
** {{miss|}} Build a common harness for Python and NodeJS Marionette tests, and enable them to run on devices and emulators
*** on-track for delivery in early Q3

* Performance
** {{done|}} Deploy a Talos dashboard that will allow Talos regressions to be more easily "sheriffed"
** {{done|}} Improve Eideticker's ability to scale
** {{done|}} Prototype Datazilla alerts for Talos and Eideticker data

* Mobile
** {{done|}} Move Android 2.3 reftests off of tegras
** {{done|}} Designate autophone and/or Eideticker as official perf systems for Android 2.3

* Bugzilla
** {{done|}} Migrate BMO and upstream Bugzilla CI from Tinderbox to travis-ci.
** {{done|}} Continue and deepen analysis of BMO perf data.
** {{done|}} Determine list of possible improvements, estimate gains, prioritize, and implement.

* Treeherder
** {{done|}} Deploy a production version of Treeherder in coordination with Laura's team
** {{miss|}} Define and implement a sheriff transition plan to move from TBPL to Treeherder
*** Production deployment took much longer than anticipated; sheriff transition to occur in first half of Q3
** {{done|}} Have Treeherder report data to OrangeFactor

* Community
** {{done|}} Refresh our list of "good first bugs" on a monthly basis
** {{done|}} Review these and make sure they have adequate information for contributors to start with
** {{done|}} Keep the numbers of open good first bugs steady or increasing

=== Web Engineering ===
* crash-stats
** {{done|}} Prototype work to support 100% crash processing for support classification and better user retention after a crash [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Implement symbol upload by partners [Scale FirefoxOS]
** {{ok|}} Better search, graphs, and correlation reports to support QA and Crashkill teams [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Infrastructure improvements to support shipping engineer-requested features faster [Get Firefox on a Growth Trajectory / Scale FxOS]

* FHR
** {{done|}} Research and develop a plan for addressing sideloading [Invest in Sustainability]

* DXR
** {{miss|}} Move to a more scalable data store to enable indexing all trees [Scale FxOS]. Plugin API designed and implemented. 4 out of 5 plugins ported. ES query structure benched and proven. ES trigram-accelerated regex matching invented. To do: port indexing to ES, port clang plugin to ES, port filters to ES, port querying machinery to ES.
** {{drop|}} Implement search result mixing [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Improve documentation and install to lower the bar for contribution [Enable Communities with Impact] [http://dxr.readthedocs.org/en/latest/ Here it is.]

* l10n
** {{ok|}} (stretch) Remove dependency on buildbot [Enable Communities with Impact]

* Plugincheck
** {{done|}} Ship new version to support Firefox 29+ [Get Firefox on a Growth Trajectory]

* Air Mozilla
** {{done|}} Open event editing to all signed in users, wiki style [Enable Communities with Impact]
** {{done|}} Protoype ability to search by transcript [Enable Communities with Impact]

[https://etherpad.mozilla.org/webeng-q22014 Full list]

=== SUMO and Input ===
* SUMO
** {{drop|}} Implement interactive onboarding for new community volunteers [Enable communities with impact]
** {{ok|}} Implement an initial community hub [Enable communities with impact]
** {{done|}} Prototype BuddyUp app: interactive support for FirefoxOS [Scale FirefoxOS]

* Input
** {{done|}} Integrate with Gengo translation API to improve localization [Scale FirefoxOS]
** {{done|}} (stretch) Implement and roll out new product-centric dashboards [Scale FirefoxOS]

[https://etherpad.mozilla.org/sumodev-2014-goals Full list]

=== Release Engineering ===
* {{ok|}} Plan and implement a sustainable approach to releases on legacy Android platforms [Get Firefox on a Growth Trajectory]
* {{ok|}} Support infrastructure work on closing scl3 datacenter to save cost [Get Firefox on a Growth Trajectory]
* {{risk|}} Implement automation (slave loan tool) to reduce manual work [Get Firefox on a Growth Trajectory]
* {{ok|}} Stand up device builds for b2g reference phones [Scale FirefoxOS]
* {{done|}} Remove dependencies on and turn off deprecated systems [Get Firefox on a Growth Trajectory]
* {{ok|}} Audit monitoring and instrumentation of release systems with a view to getting better insight, enabling better agility [Scale FirefoxOS]
* {{risk|}} Continue Balrog (new AUS) rollout to beta, and prepare for release/ESR [Get Firefox on a Growth Trajectory]
* {{ok|}} Automate merge day processes [Get Firefox on a Growth Trajectory]
* Continue infrastructure improvement program:
** {{ok|}} Move more work into the cloud to reduce cost and increase agility [Scale FirefoxOS]
** {{risk|}} Improve build and test environment for Windows [Get Firefox on a Growth Trajectory]
** {{risk|}} Get taskcluster ready to replace buildbot in Q3 and Q4 [Scale FirefoxOS]
* Joint goals with A-team:
** {{ok|}} Design an API that will be the single source of truth about release information [Get Firefox on a Growth Trajectory]

[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Ajlqy6z1WDBvdGNxaFFpbnQ4UDdySzZVcGU1RkN4b0E&usp=sharing&pli=1#gid=10 Full list]

=== Release Engineering Operations ===

* Datacenter Consolidation
** {{ok| Migrate SCL1 infrastructure to SCL3 and close SCL1 datacenter. {{bug|981124}} and {{bug|961164}} [Datacenter consolidation and cost reduction] - target end date is July 14th }}
** {{done| Decommission deprecated hardware. {{bug|997213}} [Datacenter consolidation and cost reduction] }}

* Build/Test System Performance Enhancements
** {{done| Create a POC for Windows build systems on seamicro/SSD hardware and replicate to replace most of the existing Windows build infrastructure if successful. {{bug|982261}} [Get Firefox on a Growth Trajectory] }}
** {{drop| Create a POC for OS X build systems using SSD drives and replicate to the rest of the existing OS X build infrastructure if successful. {{bug|992364}} [Get Firefox on a Growth Trajectory] - build times did not expereince the expected time reduction }}
** {{drop| Architect and deploy a 3-node Ceph Prototype instance if tests on the existing POC show significant build speed increases. {{bug|995512}} [Get Firefox on a Growth Trajectory] - ceph did not prove appropriate for this use }}

* Build/Test System Self-Serve Re-architecture
** {{ok| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Growth Trajectory] }}
** {{ok| Develop a new image creation solution for 2008R2 build machines which can be used to deploy on bare metal. {{bug|798657}} [Get Firefox on a Growth Trajectory] }}

[https://etherpad.mozilla.org/relops-q22014 Full list]

=== Developer Services ===
* {{ok|}} Review and scale out git architecture [Scale FirefoxOS]
* {{ok|}} (with B-team) Improve performance and review tools for Bugzilla [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{done|}} (with A-team) Deploy better tree visualization tools [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{done|}} Plan and prototype future release engineering architecture [Get Firefox on a Growth Trajectory / Scale FirefoxOS]

[https://etherpad.mozilla.org/devservices-Q22014 Full list]

=== Security & Privacy ===
Full list here: [[SecurityEngineering/2014/Q2Goals]]

* Web Platform Security
** {{ok|plan out replacement for nsIContentPolicy and start executing}} (dri=tanvi, +sicking,ckerschb)
** {{ok|Make new CSP parser on by default in nightly}} (dri=ckerschb, +grobinson,sstamm)
** {{done|Land WebCrypto}} (dri=rbarnes) (tracking {{Bug|865789}})
* Secure Client Platform
** {{ok | (moved to blassey) Get open.h264 plugin sandboxed on windows}} [dri=sstamm, a=tabraldes]
** {{ok | (moved to blassey) sandboxing logging (warning mode or logging of violations on TBPL)}} [dri=bobowen, a=sstamm,tabraldes]
* Secure Communications
** {{done|Land key pinning}} [dri=cviecco, a=keeler,mmc]
** {{done|mozilla::pkix on by default, riding the train to 31}} [dri=keeler, a=cviecco]
** {{risk| BONUS: Deploy UI for cert error reporting}} [dri=grobinson]
* Tracking Protection / Privacy
** {{ok|Get through the [https://github.com/mozilla/lightbeam/issues/milestones next 2 releases] of Lightbeam}} [dri=mmc, a=grobinson]

=== Firefox and Platform Security ===
* {{ok|Create list of 3rd party code in Firefox with versions, upstream versions, and source locations}}
* {{prev|Create fuzzer for WebNFC}}
* {{ok|Create IndexedDB fuzzer}} (make langfuzz work for async web apis)
* {{ok|Fuzz JS on ODROID ARM hardware to find bugs masked in Simulator}}
* {{new|incorporate randomized build configs into JSFunFuzz harness}}
* {{prev|Fuzz Workers and add fuzzing support for Shared Workers}}
* {{new|Create tool to auto-incorporate .webidl interfaces into DOM fuzzer}}
* {{done|Learn peach well well enough to create new pits. Test and document use of Peach on Linux}}
* {{ok|Work with various Firefox engineering teams to develop an alternative Firefox review process}}

=== Games Program ===

* Documentation
** {{done|Emscripten Documentation}}
*** Primary goal is to get a contractor, candidate identified, statement of work underway.
** {{ok|MDN General Documentation}}
*** Resources are attached, Chris Mills is driving it and games program groups are writing articles.
* {{ok|Partner approval of first B2G Emscripten Game Project}}
** Work week completed, graphics team has some fixes for 1.4 that appear low risk and provide 10fps we needed.
** Bug count is down to a handful after the week and we will be sending a Release Candidate to Disney as soon as the graphics fixes land.
* {{done|Train up replacement for Martin on Project Management related issues.}}
** Erin training is ongoing and she is already taking the lead on projects.
** No concerns of transitioning ownership of PM issue to her at this point.
* {{ok|QA}}
** Process is being worked out using the partner project
** Still need to improve general testing of game related features but expect to complete this once partner project is shipped.
* {{prev|Game Focus Benchmarking}}
** Project currently at risk as no resources are attached to the project.
** WebGL benchmarking is not currently automated and work is stalled.

Platform/2014-Q2-Goals

2014-06-17T18:31:59Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
Items marked [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 here] with release 31 and 32 are part of the Q2 landings.

=== Layout ===

* {{ok|Table Rendering with DisplayLists}}

* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Vertical text: Implement Layout frame migration to logical coordinates https://etherpad.mozilla.org/css-writing-modes
** {{ok|convert cross-layout classes}}

* Text Performance bugs ( https://etherpad.mozilla.org/textperfworkitems )
** {{ok|large text frames / interruptible reflow}}
** {{ok|enumerated font list fixes}}

* Improve Restyling Performance
** {{ok|bug 977991, and maybe bugs 804975/977594}}

* GFx work items
** {{ok|E10S BasicCompositor}}
** {{ok|GFx tiling}}
** {{ok|Accelerated Filters}}
*** spec work
*** shader & support work

* CSS Flexbox
** {{ok|pagination}}
** recently-finalized spec changes (abspos, min-width, flex sizing) (874718, 984711, 985304)

* Animations & Transitions
** {{ok|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{ok|test_animations covering OMTA}}
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{ok|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|Spec an API for querying basic properties of running CSS animations/transitions}}

* Ship and/or unprefix:
** {{done|position:sticky}}
** {{ok|Font-features that need fallback support (eg. small-caps)}}

* 3D Transforms
** interop bugs and spec improvement (bug 976365)
** implement preserve-3d proposal
** perf work

* Font Inflation and Reflow-on-Zoom
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* CSS Projects with Adobe
** {{ok|CSS Filters}}
** {{ok|CSS Masking}}
** {{ok|CSS Compositing}}

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Fonts
** {{ok|font load events}}

=== Media ===
* {{miss|Pref on MSE/VP9 for Firefox 31}}
** Expecting to land in Firefox 32 (see below)
* {{ok|Pref on MSE/VP9 for Firefox 32}}
* {{miss|Enable MSE/MP4 on Windows for Firefox 32}}
** Expecting to land on 33

=== DOM ===
* {{ok|Implement Xrays to 3 out of the following: Functions ({{bug|976148}}), Objects ({{bug|987111}}), Array/Array-like ({{bug|987163}}), and Error ({{bug|987669}})}}
* {{risk|Get rid of the long tail of C++ objects that are still exposed to the web using XPConnect}}
** We had less time for this than expected due to a previous quarter missed goal taking longer than expected to finish up (now done). Lots of pieces moving here already though.
* {{ok|Get LeakSanitizer builds enabled by default ({{bug|988041}})}}
* {{done|Identify and fix (DOM stuff, at least) hotspots in b2g app startup (smaug)}}
* {{risk|refactor how tokenizer and tree builder use buffers to reduce memory pressure crashes (hsivonen)}}
** Henri has spent a lot of time with other responsibilities
* {{risk|Land all non-cache bits of Service Workers preffed-off (on is a bonus) on m-c (nsm)}}
** we're doing well here but we only have a few weeks left in Q2 and lots of reviews need to happen. Some in-person reviews the last week of June will help.
* {{ok|Help guide and review requestAutocomplete backend implementation ({{bug|939351}})}} (likely smaug)
** The DOM team has been responsive to requests and implementation by the Firefox team is progressing.
* {{prev|implement [http://picture.responsiveimages.org/ <picture>] ({{bug|870022}}) (johns)}}
** Things are looking good for landing here now that srcset is complete.
* {{risk|Ensure plugins are shippable for e10s}} (sort of {{bug|874016}}) (johns)
** John is working on this but <picture> took more of the quarter than expected.
* {{risk|Implement Shadow DOM :host style selector ({{bug|992245}})}} (wchen)
** wchen got caught up with other Web Components issues affecting gaia so this may not happen in Q2.
* {{done|Enable Shadow DOM for certified apps ({{bug|1000199}})}} (wchen)
* {{done|Define a plan for how to instrument code that triggers COW of pages post forking in a post Nuwa world (bonus if we can actually build that tool this quarter)}}
** We have patches for this already! Not landed, but that's not our goal.

=== WebAPI ===
* {{ok|finalize moving main thread IDB to PBackground including blobs}} (bent)
** Lots of other things pulled bent away from this but it's progressing well when he has the time to work on it.
* {{risk|Convert DataStore cursors and DataStore object itself from JS to C++ (baku)}}
** DataStore Service didn't land until late in the quarter so these other parts of DataStore are at risk for landing by the end of June.
* {{risk|Finalize moving quotamanager to PBackground}} (janv)
** Jan took care of a few other pieces of the move to PBackground and once FileHandle changes land, this can happen; unlikely for the end of June.
* {{ok|clarify design and spec issues around Fetch for Service Workers to ensure they're implementable}} (annevk)
** Good progress is being made here.
* {{risk|implement gecko side of [http://w3c.github.io/manifest/ manifest] spec}} ({{bug|997779}}) (marcosc)
** Implement processing of V1 members (name, orientation, display, icons, start_url).
** Finish implementation by Monday, June 30.
** This is waiting on reviews and with vacation, is at risk for happening by the end of June.
* {{risk|finish [https://w3c.github.io/screen-orientation/ device orientation] spec with Mounir}} (marcosc)
** Write tests for all conformance requirements.
** Publish LC by Monday, June 30.
** work has been done here and is waiting on the review of others and integration afterward

=== JS ===
* {{jok|941796}} Generational GC on Firefox OS 2.0 [Scale FirefoxOS]

=== Accessibility ===
* {{ok|Sandboxing support: create and update cached structure of the accessible tree in the parent process (tbsaunde)}}
* {{prev|Windows support: Land basic UIA text navigation implementation (surkov)}}
* {{ok|FFOS/GAIA: fix 9 [http://mzl.la/1g3rSJs P1 Gaia accessibility bugs] (there are 9 total at time of writing)}}
** Priorities may shift as there is flux and possible force multiplier work (e.g. web components).

=== Perf ===

* Improve Firefox responsiveness & startup time:
** Finish session-store work:
*** {{risk|Improve session-store startup time {{bug|987592}} }}
*** {{ok|Store less data in the sessionstore.js file {{bug|943352}} }}
*** {{ok|Break up janky operations into smaller chunks {{bug|984886}} }}
** Start eliminating top main-thread I/O offenders reported to Telemetry {{bug|572459}}:
*** 1. {{done|Remove main-thread IO from background update of {profile}\blocklist.xml {{bug|989419}} }}
*** 2. {{done|Avoid main-thread IO in Sync code {{bug|988301}} }}
*** 3. {{done|Avoid main-thread IO for {profile}\addons.json {{bug|988292}} }}
*** 4. {{done|Search service was falling back to synchronous initialization {{bug|785487}} }}
*** 5. {{done|User dictionary (persdict.dat) read on the main thread {{bug|880864}} }}
*** 6. {{done|Avoid main-thread IO for {profile}\blocklist.xml {{bug|988304}} }}
** {{ok|New storage system for prefs {{bug|897049}} }}
** {{done|The add-on compatibility dialog should not interrupt startup unless strictly necessary {{bug|760356}} }}
** {{ok|Investigate feasibility of starting Flash plugin instances asynchronously {{bug|998863}} }}

* Fill gaps in test coverage (vs press benchmarks) and prevent regressions:
** {{ok|Create a Talos test for "cold" startup time {{bug|936617}} }}
** {{done|Create a Talos test for time to restore a previous session {{bug|936630}} }}
** {{done|Integrate our new power-profiling test into the test infrastructure {{bug|962715}} }}
** {{ok|Automatically detect new sources of main-thread I/O in tests {{bug|998794}} }}
** {{done|Monitor & track regressions in important Talos tests during each release cycle}}

* Partner with other teams on projects with big perf impact
** {{ok|Assist Necko team with measuring performance of new network cache}}
** {{done|Make it easier to debug performance regressions by (optionally) capturing profiles during Talos tests {{bug|967619}} }}
** {{ok|Expand use of the T100 tablet/laptop as a reference slow device}}
** {{ok|Work with fx-team on ongoing regressions}}
** {{ok|Add performance tests for OMTC/APZC}}

* Study impact of extensions on Firefox performance
** {{ok|Create a Telemetry dashboard to expose add-ons' impact on Firefox startup time}}

* Grow community:
** {{ok|Mentor at least 5 new external contributors}}

=== Networking ===

* {{ok|Mitigate CSRF attacks against internal networks (block rfc 1918 local addresses from non-local addresses) ({{bug|354493}}) (sworkman) }}
* {{done|HTTP/2: implement draft-11 of HTTP/2 spec and continue participating in spec development. (hurley / mcmanus) }}
* {{done|Turn on new HTTP cache in nightly (honza / michal) }}
* {{ok| NetworkLinkService should be enabled so Necko can respond to network changes ({{bug|939318}}) (bagder) }}
* {{ok|B2G: Provide way to "set network offline" per app ({{bug|786419}}) (valentin) }}
* {{drop|Gather data and produce a report on performance wins vs resource costs of the seer on several desktop and mobile scenarios. (hurley) }}
** We've decided to re-name the seer the "network predictor" and to re-write it using the HTTP cache instead of SQLite, with Q3 target. So no performance numbers will be available this quarter.

=== Mobile ===
=== A*Team ===
full list: [[Auto-tools/Goals/2014Q2]]

* B2G
** {{ok|}} Deliver v2 of the FxOS Certification Suite
** {{ok|}} Build a common harness for Python and NodeJS Marionette tests, and enable them to run on devices and emulators

* Performance
** {{done|}} Deploy a Talos dashboard that will allow Talos regressions to be more easily "sheriffed"
** {{ok|}} Improve Eideticker's ability to scale
** {{ok|}} Prototype Datazilla alerts for {{done|}}Talos and {{ok|}}Eideticker data

* Mobile
** {{done|}} Move Android 2.3 reftests off of tegras
** {{ok|}} Designate autophone and/or Eideticker as official perf systems for Android 2.3

* Bugzilla
** {{done|}} Migrate BMO and upstream Bugzilla CI from Tinderbox to travis-ci.
** {{ok|}} Continue and deepen analysis of BMO perf data.
** {{ok|}} Determine list of possible improvements, estimate gains, prioritize, and implement.

* Treeherder
** {{ok|}} Deploy a production version of Treeherder in coordination with Laura's team
** {{ok|}} Define and implement a sheriff transition plan to move from TBPL to Treeherder
** {{ok|}} Have Treeherder report data to OrangeFactor

* Community
** {{done|}} Refresh our list of "good first bugs" on a monthly basis
** {{done|}} Review these and make sure they have adequate information for contributors to start with
** {{ok|}} Keep the numbers of open good first bugs steady or increasing

=== Web Engineering ===
* crash-stats
** {{done|}} Prototype work to support 100% crash processing for support classification and better user retention after a crash [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Implement symbol upload by partners [Scale FirefoxOS]
** {{ok|}} Better search, graphs, and correlation reports to support QA and Crashkill teams [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Infrastructure improvements to support shipping engineer-requested features faster [Get Firefox on a Growth Trajectory / Scale FxOS]

* FHR
** {{done|}} Research and develop a plan for addressing sideloading [Invest in Sustainability]

* DXR
** {{ok|}} Move to a more scalable data store to enable indexing all trees [Scale FxOS]
** {{drop|}} Implement search result mixing [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{done|}} Improve documentation and install to lower the bar for contribution [Enable Communities with Impact] [http://dxr.readthedocs.org/en/latest/ Here it is.]

* l10n
** {{ok|}} (stretch) Remove dependency on buildbot [Enable Communities with Impact]

* Plugincheck
** {{done|}} Ship new version to support Firefox 29+ [Get Firefox on a Growth Trajectory]

* Air Mozilla
** {{done|}} Open event editing to all signed in users, wiki style [Enable Communities with Impact]
** {{done|}} Protoype ability to search by transcript [Enable Communities with Impact]

[https://etherpad.mozilla.org/webeng-q22014 Full list]

=== SUMO and Input ===
* SUMO
** {{drop|}} Implement interactive onboarding for new community volunteers [Enable communities with impact]
** {{ok|}} Implement an initial community hub [Enable communities with impact]
** {{done|}} Prototype BuddyUp app: interactive support for FirefoxOS [Scale FirefoxOS]

* Input
** {{done|}} Integrate with Gengo translation API to improve localization [Scale FirefoxOS]
** {{done|}} (stretch) Implement and roll out new product-centric dashboards [Scale FirefoxOS]

[https://etherpad.mozilla.org/sumodev-2014-goals Full list]

=== Release Engineering ===
* {{ok|}} Plan and implement a sustainable approach to releases on legacy Android platforms [Get Firefox on a Growth Trajectory]
* {{ok|}} Support infrastructure work on closing scl3 datacenter to save cost [Get Firefox on a Growth Trajectory]
* {{risk|}} Implement automation (slave loan tool) to reduce manual work [Get Firefox on a Growth Trajectory]
* {{ok|}} Stand up device builds for b2g reference phones [Scale FirefoxOS]
* {{done|}} Remove dependencies on and turn off deprecated systems [Get Firefox on a Growth Trajectory]
* {{ok|}} Audit monitoring and instrumentation of release systems with a view to getting better insight, enabling better agility [Scale FirefoxOS]
* {{risk|}} Continue Balrog (new AUS) rollout to beta, and prepare for release/ESR [Get Firefox on a Growth Trajectory]
* {{ok|}} Automate merge day processes [Get Firefox on a Growth Trajectory]
* Continue infrastructure improvement program:
** {{ok|}} Move more work into the cloud to reduce cost and increase agility [Scale FirefoxOS]
** {{risk|}} Improve build and test environment for Windows [Get Firefox on a Growth Trajectory]
** {{risk|}} Get taskcluster ready to replace buildbot in Q3 and Q4 [Scale FirefoxOS]
* Joint goals with A-team:
** {{ok|}} Design an API that will be the single source of truth about release information [Get Firefox on a Growth Trajectory]

[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Ajlqy6z1WDBvdGNxaFFpbnQ4UDdySzZVcGU1RkN4b0E&usp=sharing&pli=1#gid=10 Full list]

=== Release Engineering Operations ===

* Datacenter Consolidation
** {{ok| Migrate SCL1 infrastructure to SCL3 and close SCL1 datacenter. {{bug|981124}} and {{bug|961164}} [Datacenter consolidation and cost reduction] }}
** {{done| Decommission deprecated hardware. {{bug|997213}} [Datacenter consolidation and cost reduction] }}

* Build/Test System Performance Enhancements
** {{done| Create a POC for Windows build systems on seamicro/SSD hardware and replicate to replace most of the existing Windows build infrastructure if successful. {{bug|982261}} [Get Firefox on a Growth Trajectory] }}
** {{drop| Create a POC for OS X build systems using SSD drives and replicate to the rest of the existing OS X build infrastructure if successful. {{bug|992364}} [Get Firefox on a Growth Trajectory] }}
** {{drop| Architect and deploy a 3-node Ceph Prototype instance if tests on the existing POC show significant build speed increases. {{bug|995512}} [Get Firefox on a Growth Trajectory] - ceph did not prove appropriate for this use }}

* Build/Test System Self-Serve Re-architecture
** {{ok| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} [Get Firefox on a Growth Trajectory] }}
** {{ok| Develop a new image creation solution for 2008R2 build machines which can be used to deploy on bare metal. {{bug|798657}} [Get Firefox on a Growth Trajectory] }}

[https://etherpad.mozilla.org/relops-q22014 Full list]

=== Developer Services ===
* {{ok|}} Review and scale out git architecture [Scale FirefoxOS]
* {{ok|}} (with B-team) Improve performance and review tools for Bugzilla [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{done|}} (with A-team) Deploy better tree visualization tools [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{done|}} Plan and prototype future release engineering architecture [Get Firefox on a Growth Trajectory / Scale FirefoxOS]

[https://etherpad.mozilla.org/devservices-Q22014 Full list]

=== Security & Privacy ===
Full list here: [[SecurityEngineering/2014/Q2Goals]]

* Web Platform Security
** {{ok|plan out replacement for nsIContentPolicy and start executing}} (dri=tanvi, +sicking,ckerschb)
** {{ok|Make new CSP parser on by default in nightly}} (dri=ckerschb, +grobinson,sstamm)
** {{done|Land WebCrypto}} (dri=rbarnes) (tracking {{Bug|865789}})
* Secure Client Platform
** {{ok|Get open.h264 plugin sandboxed on windows}} [dri=sstamm, a=tabraldes]
** {{prev|sandboxing logging (warning mode or logging of violations on TBPL)}} [dri=bobowen, a=sstamm,tabraldes]
* Secure Communications
** {{done|Land key pinning}} [dri=cviecco, a=keeler,mmc]
** {{done|mozilla::pkix on by default, riding the train to 31}} [dri=keeler, a=cviecco]
** {{risk| BONUS: Deploy UI for cert error reporting}} [dri=grobinson]
* Tracking Protection / Privacy
** {{ok|Get through the [https://github.com/mozilla/lightbeam/issues/milestones next 2 releases] of Lightbeam}} [dri=mmc, a=grobinson]

=== Firefox and Platform Security ===
* {{ok|Create list of 3rd party code in Firefox with versions, upstream versions, and source locations}}
* {{prev|Create fuzzer for WebNFC}}
* {{ok|Create IndexedDB fuzzer}} (make langfuzz work for async web apis)
* {{ok|Fuzz JS on ODROID ARM hardware to find bugs masked in Simulator}}
* {{new|incorporate randomized build configs into JSFunFuzz harness}}
* {{prev|Fuzz Workers and add fuzzing support for Shared Workers}}
* {{new|Create tool to auto-incorporate .webidl interfaces into DOM fuzzer}}
* {{new|Work toward fuzzing HTTP 2.0}}
* {{ok|Work with various Firefox engineering teams to develop an alternative Firefox review process}}

=== Games Program ===

* Documentation
** {{ok|Emscripten Documentation}}
*** Primary goal is to get a contractor, candidate identified, statement of work underway.
** {{ok|MDN General Documentation}}
*** Resources are attached, Chris Mills is driving it and games program groups are writing articles.
* {{ok|Partner approval of first B2G Emscripten Game Project}}
** Work week completed, graphics team has some fixes for 1.4 that appear low risk and provide 10fps we needed.
** Bug count is down to a handful after the week and we will be sending a Release Candidate to Disney as soon as the graphics fixes land.
* {{ok|Train up replacement for Martin on Project Management related issues.}}
** Erin training is ongoing and she is already taking the lead on projects.
** No concerns of transitioning ownership of PM issue to her at this point.
* {{ok|QA}}
** Process is being worked out using the partner project
** Still need to improve general testing of game related features but expect to complete this once partner project is shipped.
* {{prev|Game Focus Benchmarking}}
** Project currently at risk as no resources are attached to the project.
** WebGL benchmarking is not currently automated and work is stalled.

Platform/2014-Q3-Goals

2014-06-10T15:19:04Z

Arich: Created page with "=== Platform === ==== 2014 General Goals ==== === GFX === === Layout === === Media === === DOM === === WebAPI === === JS === === Accessibilit..."

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===

=== Layout ===

=== Media ===

=== DOM ===

=== WebAPI ===

=== JS ===

=== Accessibility ===

=== Perf ===

=== Networking ===

=== Mobile ===

=== A*Team ===

=== Web Engineering ===

=== SUMO and Input ===

=== Release Engineering ===

=== Release Engineering Operations ===

=== Developer Services ===

=== Security & Privacy ===

=== Firefox and Platform Security ===

=== Games Program ===

Platform/2014-Q2-Goals

2014-06-09T13:16:37Z

Arich: /* Release Engineering Operations */

Automatic creation of images with puppet, MDT

2014-06-02T23:23:28Z

Arich:

This document describes the plan for building Windows images for bare metal provisioning.

The intention is to build a modular and repeatable image build process using Microsoft Deployment Workbench (MDT) and Puppet but without Group Policy or other services that require joining a Microsoft Domain. The overall build process will rely heavily on Puppet to provide more visibility and accessibility to our configuration for Windows Operating Systems.

'''Assumptions'''
* There is no intention to join machines to a domain or provide ongoing configuration management with GPO or puppet. Changes will require the building and deployment of new images, similar to AMIs in AWS.
* Building the image will be broken down into two MDT task sequences to capture images. The first task sequence will create the base image. By using a base image we will cut down time spent to recapture deploy images when changes are need and gives us a point to diverge when needing to create multiple versions of an OS The second image will include software installed and modifications made by puppet and will be the one that is deployed to bare-metal nodes. This second image will include Loaner and other divergent configs.
* The creation of the second image should be able to be completely automated. With the workflow of: Make a change to puppet, request an image be created, get an image with the new puppet config applied.
* Puppet will provide a common, publicly discoverable configuration point for windows as well as linux and OS X, allowing modification of the system configuration by people other than Windows administrators.
* The 2008r2 builder image is the one currently being reworked to fit into the above mentioned architecture (per Tara's request) . Once complete, this will provide us with a template to start for other Windows OSes, but there will be varying degrees of changes required depending upon the OS and tester vs builder configurations.

'''Image Build Steps'''
* The first task sequence or base task sequence
** Installs and builds onto the out-of-box Windows Image
** Will consist of:
*** The installation of large applications that is unlikely to change for extended periods of time
**** Such as Microsoft Visual Studio
*** The installation of unlikely to change developer tools
**** Such as Microsoft Direct X SDK
*** The installation of Microsoft updates
**** This will install the pre-approved updates from our WSUS server
**** In this task sequence Windows is configured to talk to our server and run a one time update
*** Application or tools that may be useful during the Deploy task sequence or troubleshooting in case image capture fails
*** An Image capture of the above
* The second task sequence or deploy task sequence
** Installs and builds onto the base image
** Will consists of:
*** Installation and configuration of Puppet
*** One time Puppet run
**** The majority of OS configuration, application install, and file management will be handled here
*** A full sysprep
*** Init scripts capture for bootstrap for both cloud and baremetel installs
**** Used for host naming, etc
**** Will need to to be versatile enough to work with multiple hooks.
*** An image capture of the final deploy image

In theory the deploy image will be deploy-able by Ironic. Though this is still needed to be tested once ironic supports whole disk images. Also the deploy image can be deployed to a VM and recaptured to create a cloud deploy-able image such as an ami should we later decide to replicate this into a cloud infrastructure.

'''Costs/Risks'''
* There may be issues with the number of registrations with KMS because we are redeploying an image instead of building a new image on each deploy
* The machine naming sysprep/init script will need to be reworked and executed in a different manner than we currently use for deployment
* Actual deployment of images will rely on the ability of openstack/Ironic to deploy whole disk images

[[https://infra.etherpad.mozilla.org/925080|Task tracking etherpad]]

Create staging network, ironic-based openstack deployment, and provide support for prototype provisioning for ubuntu 12.04

2014-06-02T23:20:25Z

Arich: Created page with "This document describes the design options for using Openstack to provide a common end-user API to facilitate self service across the Mozilla build/test environment '''Recomm..."

This document describes the design options for using Openstack to provide a common end-user API to facilitate self service across the Mozilla build/test environment

'''Recommended solution: Non-SDN Design'''
4 new VLANs minimum
* Core
* Try
* Loaner
* Admin
** connects all administration hosts (eg. Conductors, Compute hosts)
** All admin hosts are ESX VMs
** Secondary NICs connect to core, try, and loaner networks as necessary for DHCP/TFTP

Default GW for all VLANs is the releng fw ( Non Neutron )
Each VLAN is isolated as a separate AZ with openstack
IMPI, iLO, PDUs, etc. are on the existing releng BU 'inband' VLAN (these can be outband as long as they are routeable. no need to have them on the same VLAN)

For loaners, BM nodes can use standard scheduler to loan out
For production, each BM will be requested through the standard Openstack scheduler but will be filtered down to a metadata tag unique to each BM node (eg. asset tag, serial) via individual aggregate groups or some other scheduler filter
* Our 2 options for doing this are:
** create a AZ for each node. When requesting a node, the caller must call an AZ (node) within the group needed (eg. AZ = nodeXYZ, which is within Try VLAN)
** Write a secondary filter similar to a AZ but one that would be exposed to the end user

Bare metal nodes will be grouped to an AZ matching the VLAN
When requesting an AZ or a single node through a node dedicated AZ, caller must also select a matching network the the network the node is located on
Additional aggregate host groups will define hardware groups (mac mini rX, ix7000, etc)

DHCP will be provided through each conductor and all VLANs containing BM nodes should forward DHCP traffic to all conductors via DHCP helpers

'''Networks'''
** These sizes may need adjustment based on host counts + moderate growth
** /21 = try.cloud.releng.scl3.mozilla.com
** /22 = core.cloud.releng.scl3.mozilla.com
** /23 = loaner.cloud.releng.scl3.mozilla.com
** /23 = admin.cloud.releng.scl3.mozilla.com

'''Decisions/Assumptions'''
* Network traffic should not flow through Linux hosts, because we don't have the skill or hardware support to handle the massive data flows that would result
* Avoid SDN, for similar reasons. If we do have to do SDN, do it using "normal" OpenStack tools operating on dedicated network hardware, rather than trying to build a solution that will work for all of Mozilla's systems.
* While isolating each host from all others is desirable, it is difficult given the above decisions, so we will fall back to the current level of isolation: hosts at each trust level can only communicate with other hosts at that trust level
* The scheduling implementation relies on deployment of taskcluster, or a tool like it, that will interface properly with the dynamic provisioning API

'''Notes'''
* "loaner" is considered a different trust level than "try", so loaner hosts must be isolated from try, in a distinct VLAN. Moves between VLANs are manual and rare, so that VLAN needs to have a minimum pool of dedicated hosts for each platform, unlike the current practice of taking specific machines out of production and then adding them back in.

'''Costs/Risks'''
* Need some time from netops to set up networks/VLANs/flows
* Solution is based on icehouse (just released) and ironic (beta), so lots of bugs and issues are expected
* Significant development work required to support more than Ubuntu installs
* Interfacing with existing deployment tools such as JAMF and WDS is an unknown

'''Alternatives'''
* Use SDN to allow bare metal hosts' VLANs to be changed dynamically
** costs/risks: configuring SDN, probably with dedicated network hardware
*** unfamiliar technology
*** needs time from netops, dcops
*** definitely needs dedicated switches; may require dedicated firewall
*** may not work
** benefit: all nodes can be in the same AZ
** timeline: plus quarters, depending on how much needs to be dedicated hardware
* configure one VLAN per host with SDN on the firewall
** costs/risks: SDN configuration
*** unfamiliar technology
*** security issues with dynamic configuration of firewalls
*** must interact with netops to establish SDN techniques
*** high-risk work: firewall changes generally require TCWs, so we'll wait for a TCW for every incremental change
*** expensive option: purchase a staging firewall to test against
*** may not work
** benefit: inter-node network isolation
** timeline: plus several quarters
** 4000 vlan limitation
* configure one VLAN per host with flows through neutron
** costs/risks: neutron configuration, building appropriate neutron hardware
*** high-volume network flows require extensive tuning
*** HA is hard to achieve at this level
*** may not be possible with neutron and without SDN
*** may not even be possible with SDN
** benefit: inter-node network isolation
** timeline: plus several months, if it works

'''Next Steps'''
* Choose a preferred solution
* Build the prototype out in puppet
** Install process should be easily customized with local patches and/or custom components -- so don't use upstream packages verbatim
** Be generic enough that another organization can use the same modules to install a more "normal" openstack (e.g., webeng may be interested)
** Something functional in a matter of 2-3 weeks
* Build out infrastructure
** VLANs + plumbing for ESX, firewall
** Flow Requests
** Set up with hosts in place in 1-2 weeks
* After:
** Begin working on back end drivers
*** timeline depends on level of engineering assistance, compatibility of existing tools like JAMF, WDS, etc.

'''Open Questions'''
* does ironic support AZ conductor isolation so bm node X in vlan A gets mapped to a conductor in Vlan A
** Ironic has no knowledge of host aggregation boundaries.
* Do conductors have to be in the same VLAN, or can we get away with DHCP helpers?
** Because Ironic has no knowledge of host aggregation boundaries, conductors should not be isolated to separate VLANs. We should use DHCP helpers to forward the traffic to all conductors

ReleaseOperations/Projects/AutomaticProvisioning

2014-06-02T23:09:42Z

Arich: /* 2014Q2 */

== Description ==

AutomaticProvisioning is the umbrella project for supporting dynamic provisioning of systems within the releng infrastructure. This will include hosts with all supported operating systems (Windows, OS X, and Linux) on a variety of hardware and virtualization platforms (server hardware, Macs, VMware, AWS) as well as mobile testing hardware such as panda boards and tegras.

This is the infrastructure sister project to [[Auto-tools/Projects/TaskCluster]]. Both fall under a larger initiative to improve the efficiency and cost-effectiveness of building and testing for Firefox and Firefox OS.

Two other related but out-of-scope projects are:
* Direct Connection to Amazon
* Deploying a local Blob Storage engine

== Docs ==

* [https://etherpad.mozilla.org/2014-goal-improved-testing notes from initial discussion]
* [https://etherpad.mozilla.org/2014-goal-improved-testing-relops more notes from discussion within relops]

== Status Meetings ==

* [[ReleaseOperations/Projects/AutomaticProvisioning/Meetings]]

== Schedule ==

(tentative of course)

=== 2014Q1 ===
* Be able to provision Linux instances on a single 4-node iX server chassis via an API call
** No automatic support for creating images
** No support for changing VLANs (but planning for this is underway)

=== 2014Q2 ===
* [[Automatic creation of images with puppet, MDT|Automatic creation of windows images with puppet, MDT]]
* [[Create staging network, ironic-based openstack deployment, and provide support for prototype provisioning for ubuntu 12.04]]

== Tasks ==
* look at provisioning tools / cloud stacks -- jake/dustin
* moving things out of GPO and into puppet or MDT (difficult with Win8 - registration of default browsers is domain-only) --Q
* continue with puppet on windows, with different focus (puppet doesn't run on prod instances) --mark
* plan for VLAN changes, but no implementation this quarter --adam

== Components ==

TBD

Automatic creation of images with puppet, MDT

2014-06-02T23:07:19Z

Arich: Created page with "This document describes the plan for building Windows images for bare metal provisioning. The intention is to build a modular and repeatable image build process using Micros..."

ReleaseOperations/Projects/AutomaticProvisioning

2014-06-02T23:04:03Z

Arich: /* 2014Q2 */

== Description ==

AutomaticProvisioning is the umbrella project for supporting dynamic provisioning of systems within the releng infrastructure. This will include hosts with all supported operating systems (Windows, OS X, and Linux) on a variety of hardware and virtualization platforms (server hardware, Macs, VMware, AWS) as well as mobile testing hardware such as panda boards and tegras.

This is the infrastructure sister project to [[Auto-tools/Projects/TaskCluster]]. Both fall under a larger initiative to improve the efficiency and cost-effectiveness of building and testing for Firefox and Firefox OS.

Two other related but out-of-scope projects are:
* Direct Connection to Amazon
* Deploying a local Blob Storage engine

== Docs ==

* [https://etherpad.mozilla.org/2014-goal-improved-testing notes from initial discussion]
* [https://etherpad.mozilla.org/2014-goal-improved-testing-relops more notes from discussion within relops]

== Status Meetings ==

* [[ReleaseOperations/Projects/AutomaticProvisioning/Meetings]]

== Schedule ==

(tentative of course)

=== 2014Q1 ===
* Be able to provision Linux instances on a single 4-node iX server chassis via an API call
** No automatic support for creating images
** No support for changing VLANs (but planning for this is underway)

=== 2014Q2 ===
* [[Automatic creation of images with puppet, MDT]]
* [[Support prototype provisioning for ubuntu 12.04]]

== Tasks ==
* look at provisioning tools / cloud stacks -- jake/dustin
* moving things out of GPO and into puppet or MDT (difficult with Win8 - registration of default browsers is domain-only) --Q
* continue with puppet on windows, with different focus (puppet doesn't run on prod instances) --mark
* plan for VLAN changes, but no implementation this quarter --adam

== Components ==

TBD

Platform/2014-Q2-Goals

2014-06-02T21:18:37Z

Arich: /* Release Engineering Operations */

Platform/2014-Q2-Goals

2014-05-05T19:45:49Z

Arich: /* Release Engineering Operations */

CIDuty/Other Duties

2014-05-05T16:40:44Z

Arich: /* Update mobile talos webhosts */

__TOC__

= Tree Maintenance =
== Repo Errors ==
If a dev reports a problem pushing to hg (either m-c or try repo) then you need to do the following:
* File a bug (or have dev file it) and then poke in #ops noahm
** If he doesn't respond, then escalate the bug to page on-call
* Follow the steps below for "How do I close the tree"

== How do I see problems in TBPL? ==
All "infrastructure" (that's us!) problems should be purple at http://tbpl.mozilla.org. Some aren't, so keep your eyes open in IRC, but get on any purples quickly.
== How do I close the tree? ==
See [[ReleaseEngineering/How_To/Close_or_Open_the_Tree]]

== How do I claim a rentable project branch? ==
See [[ReleaseEngineering/DisposableProjectBranches#BOOKING_SCHEDULE]]

== Clean up the scheduler DB ==
Sometimes we get some jobs pending for days:
https://secure.pub.build.mozilla.org/buildapi/pending

These are supposed to be cleaned up automatically now. See {{bug|755012}} for details.

= Re-run jobs =
== How to trigger Talos jobs ==
see [[ReleaseEngineering/How_To/Trigger_Talos_Jobs]]

== How to re-trigger all Talos runs for a build (by using sendchange) ==
see [[ReleaseEngineering/How_To/Trigger_Talos_Jobs]]

== How to re-run a build ==
Do ''not'' go to the page of the build you'd like to re-run and cook up a sendchange to try to re-create the change that caused it. Changes without revlinks trigger releases, which is not what you want.

Find the revision you want, find a builder page for the builder you want (preferably, but not necessarily, on the same master), and plug the revision, your name, and a comment into the "Force Build" form. <em>Note that the '''YOU MUST''' specify the branch, so there's no null keys in the builds-running.js.</em> Otherwise your build will not show up in self-serve or tbpl.

= Nightlies =

== How do I re-spin mozilla-central nightlies? ==
=== To rebuild the same nightly for some platform ===
buildbot's Rebuild button works fine. BUT, if the original build uploaded files or published updates you don't want to do this (caching on ftp.m.o will mean the old file is served for some time). Check the log of the original build - if it failed before uploading it's OK to rebuild.

=== To build new nightlies ===
NB: For b2g, the revision set can only be the mercurial gecko revision.

==== To build nightlies on all the platforms ====
Use [https://secure.pub.build.mozilla.org/buildapi/self-serve/mozilla-central/ self-serve] for this. Scroll to the bottom of the page and put the requested revision into the box next to ''Create new nightly builds on mozilla-central revision''. Click on the Submit button. This takes care of using the same buildID for all builds.

==== To rebuild some subset of all the nightly builders (eg only desktop/Android/b2g) ====
To reach a specific nightly builder on a build master, you can use a finished nightly job on tbpl and this snippet of javascript code (add it to the bookmark toolbar):
javascript:(function(){function%20JSONRequest(url,callback){var%20req=new%20XMLHttpRequest();req.open('GET',url+'?format=json');req.withCredentials=true;req.timeout=5000;req.onreadystatechange=function(){if(req.readyState===4){if(req.status!==200||!req.responseText){if(req.status===0){alert('Self-Serve%20API%20request%20timed%20out.');}else{alert('Self-Serve%20API%20request%20failed%20('+req.status+').%20\nIs%20the%20job%20still%20pending?%20\n\n'+req.responseText);}return;}try{callback(JSON.parse(req.responseText));}catch(e){alert(e);}}};req.send();}function%20openJob(job){var%20bm=job.claimed_by_name.split(':');var%20port=/build[0-9]/.test(bm[1])?"8001":/try[0-9]/.test(bm[1])?"8101":/tests[0-9]/.test(bm[1])?"8201":'unknown';window.open('http://'+bm[0]+':'+port+'/builders/'+job.buildername+'/builds/'+job.buildnumber);}function%20openCompletedJob(jobs){var%20selectedJob=UserInterface._activeResultObject();var%20startTime=Date.parse(selectedJob.startTime)/1000;jobs=jobs.filter(function(j){return(j.buildername===selectedJob.machine.name)&&((j.starttime-startTime)<=1);});if(jobs.length!==1){alert('Should%20have%20found%20exactly%20one%20matching%20job,%20found%20'+jobs.length+'!');return;}openJob(jobs[0]);}var%20id=(typeof%20UserInterface!=="undefined")?UserInterface._activeResult:'';if(!id){alert('Error%20-%20are%20you%20on%20TBPL%20with%20a%20job%20selected?');return;}var%20baseURL='https://secure.pub.build.mozilla.org/buildapi/self-serve/'+UserInterface.treeInfo.buildbotBranch;var%20re=/^(?:running|pending)-/;if(!re.test(id)){var%20rev=UserInterface._activeResultObject().revs[UserInterface.treeInfo.primaryRepo];JSONRequest(baseURL+'/rev/'+rev,openCompletedJob);}else{JSONRequest(baseURL+'/build/'+id.replace(re,''),openJob);}})()

You will need to force the specific builders on a build master, setting several parameters. First open a waterfall page (eg [http://buildbot-master82.build.mozilla.org:8001/waterfall?category=mozilla-central&num_events=0 mozilla-central]) and search for 'nightly'. Open each builder you want in a new tab.

For each builder you should set
* 'Your name' to your name
* 'Reason for build' to 'bug ###' or 'requested by <someone>'
* 'Branch to build' to 'mozilla-central' (other branches may have a prefix, eg releases/mozilla-aurora)
* 'Revision to build' to the <revision>
* 'Property 1': 'Name' to 'buildid', 'Value' to the current Pacific time (eg from running <tt>TZ=US/Pacific date +%Y%m%d%H%M%S</tt>)
Then click on the 'Force build' button.

The first two are nice-to-have for later debugging. The branch and revisions are required so that TBPL shows the builds while they are pending and running (rather than just after completion). Setting the buildid property the same across all builds helps keep nightlies consistent. An add-on like [https://addons.mozilla.org/en-US/firefox/addon/autofill-forms/ AutoFill Forms] is invaluable in storing these values and filling the form for you, but there is probably a way to do this with curl too (it's a POST).

== Disable updates ==

See [[ReleaseEngineering/How_To/Shut_off_all_updates]] for global shutoff. We use Balrog now for nightly & aurora updates.

= Talos =
== How to update the talos zips ==
We only need to do this for mobile requests.

'''This deployment is super safe. NPOTB'''

<pre>
# running this from cruncher is faster than downloading/uploading from your localhost
ssh -A cruncher
export URL=http://people.mozilla.org/~jmaher/taloszips/zips/talos.07322bbe0f7d.zip
export TALOS_ZIP=`basename $URL`
wget $URL
#relengwebadmn has limited access to the internet - that is why we scp from another host
scp ${TALOS_ZIP} relengwebadm.private.scl3.mozilla.com:/mnt/netapp/relengweb/talos-bundles/zips
ssh relengwebadm.private.scl3.mozilla.com "chmod 644 /mnt/netapp/relengweb/talos-bundles/zips/${TALOS_ZIP}"
ssh relengwebadm.private.scl3.mozilla.com "sha1sum /mnt/netapp/relengweb/talos-bundles/zips/${TALOS_ZIP}"
curl -I http://talos-bundles.pvt.build.mozilla.org/zips/${TALOS_ZIP}
</pre>

For talos.zip changes: Once deployed, notify the a-team and let them know that they can land at their own convenience.

* Please verify the shasum matches what is in the [[https://bugzilla.mozilla.org/show_bug.cgi?id=1002780#c6 comment]], we have had a few instances where the talos.zip was incorrect.

== Update mobile talos webhosts ==

Keep track of what revisions is being run.
Copy/paste the output into the bug.
Please update our [[ReleaseEngineering/Maintenance#Mobile_talos_webhost|maintenance page]]

'''This could affect mobile talos numbers or break the jobs altogether. Please coordinate with sheriffs'''

'''NOTE: There's a great deal of data we can not check into revision control for legal reasons, so there's an extensive .hgignore file. If you're adding new data to the tree that can not be checked in, please ask a talos developer/reviewer or [[https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&component=Talos file a bug]] to request any [[http://hg.mozilla.org/build/talos/file/8d6fb3704417/.hgignore .hgignore]] changes'''

=== webapp cluster ===

ssh relengwebadm.private.scl3.mozilla.com
sudo su -
cd /data/releng/src/talos-remote/www/talos-repo
# NOTICE that we have uncommitted files
hg status
# Take note of the current revision to revert to (just in case)
hg id
hg pull -u
# 488bc187a3ef tip
# ..capture the output here; the remainder will be long and not that useful..
/data/releng/src/talos-remote/update

= TBPL =
== How to deploy changes ==
RelEng no longer has access to do this. TBPL devs will request a push from Server Ops.

== How to hide/unhide builders ==
* In the 'Tree Info' menu select 'Open tree admin panel'
* Filter/select the builders you want to change
* Save changes
* Enter the sheriff password and a description (with bug number if available) of your changes
* CC :edmorley & :philor on the relevant bug so that they know what to expect when sheriffing.

= Ganglia =
* if you see that a host is reporting to ganglia in an incorrect manner it might just take this to fix it (e.g. {{bug|674233}}):
switch to root, service gmond restart

= Queue Directories =
* [https://wiki.mozilla.org/ReleaseEngineering/Queue_directories Queue directories]

If you see this in #build:

<nagios-sjc1> [54] buildbot-master12.build.scl1:Command Queue is CRITICAL: 4 dead items

It means that there are items in the "dead" queue for the given master. You need to look at the logs and fix any underlying issue and then retry the command by moving *only* the json file over to the "new" queue. See the [https://wiki.mozilla.org/ReleaseEngineering/Queue_directories Queue directories] wiki page for details.
= Cruncher =
If you get an alert about cruncher running out of space it might be a sendmail issue (backed up emails taking up too much space and not getting sent out):

<nagios-sjc1> [07] cruncher.build.sjc1:disk - / is WARNING: DISK WARNING - free space: / 384 MB (5% inode=93%):
As root:
du -s -h /var/spool/*
# confirm that mqueue or clientmqueue is the oversized culprit
# stop sendmail, clean out the queues, restart sendmail
/etc/init.d/sendmail stop
rm -rf /var/spool/clientmqueue/*
rm -rf /var/spool/mqueue/*
/etc/init.d/sendmail start

= hg<->git conversion =
This is a production system RelEng built, but has not yet transitioned to full IT operation. As a production system, it is supported 24x7x365 - escalate to IT oncall (who can page) as needed.

We'll get problem reports from 2 sources:
* via email from vcs2vcs user to release+vcs2vcs@m.c - see [[ReleaseEngineering/How_To/Process_release_email|email handling]] instructions for those.
* via a bug report for a customer visible condition - this should only be if there is a new error we aren't detecting ourselves. See the resources below and/or page hwine.

Documentation for this system:
* [http://people.mozilla.com/~hwine/tmp/vcs2vcs/ recent docs] ([http://people.mozilla.org/~hwine/tmp/vcs2vcs/trouble_shooting.html troubleshooting])
* source code: http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/
* config files: http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/

All services run as user vcs2vcs on one of the following hosts (as of 2013-01-07): github-sync1-dev.dmz.scl3.mozilla.com, github-sync1.dmz.scl3.mozilla.com, github-sync2.dmz.scl3.mozilla.com, github-sync3.dmz.scl3.mozilla.com.

== Handling alert_major_errors ==

# SSH as yourself to the hostname in the 'from' address of the alert_major_errors email.
$ ssh yourname@github-sync3.dmz.scl3.mozilla.com
$ sudo su - vcs2vcs
$ cd etc
# find the repo name that vcs2vcs is complaining about. For example:
$ grep releases-mozilla-central-no-cvs *
job02_cmds:# "hg:$HOME/repos/releases-mozilla-central-no-cvs" "github"
# discover where that job runs
$ grep job02 status
job02_cmds,github-sync3.dmz.scl3.mozilla.com,m-c w/o cvs as used by b2g
# connect to that host the same as we did above (if not already connected)
# then
$ cd logs/job02 # same job as above
$ show_update_errors update.log
# Note: the command exit code precedes the command itself
# eg. ...;255;hg --cwd...

Continue with instructions [http://people.mozilla.com/~hwine/tmp/vcs2vcs/trouble_shooting.html#repo-copy-not-updating here].

= disable/re-enable aurora updates =
Take care of by the person doing the final release since merge day activities are on the Monday before the release.

= Upload =
== Python packages ==
{{warning|Mozharness no longer uses packages from the PuppetAgain repositories! Instead, it uses http://pypi.pub.build.mozilla.org/pub and http://pypi.pvt.build.mozilla.org/pub, both served from the same directory.}}
From your local machine:
FILE=your_python_package.tar.gz
scp $FILE $LDAP_SHORT_USERNAME@relengwebadm.private.scl3.mozilla.com:
From relengwebadm:
ssh $LDAP_SHORT_USERNAME@relengwebadm.private.scl3.mozilla.com

FILE=your_python_package.tar.gz
sudo mv -vi $FILE /mnt/netapp/relengweb/pypi/pub/
sudo chmod 644 /mnt/netapp/relengweb/pypi/pub/$FILE

From your local machine:
curl -I http://pypi.pub.build.mozilla.org/pub/$FILE
# You should see "HTTP/1.1 200 OK"

== How to upload to Tooltool ==
If you don't want to upload from your own laptop (because, eg, you have a slow uplink) you can do this from cruncher.

Access cruncher with your credentials:
ME="your_short_ldap_username" # or `whoami`
ssh -A $ME@cruncher.build.mozilla.org
Download the file and then:
scp filename.tar.xz $ME@relengwebadm.private.scl3.mozilla.com:
Login to relengwebadmn:
ssh $ME@relengwebadm.private.scl3.mozilla.com
And deploy the file to tooltool:
<pre>
FILE=~/emulator.zip # or whatever you're uploading
export SHA512=`openssl sha512 $FILE | cut -d' ' -f2`
sudo mv -i $FILE /mnt/netapp/relengweb/tooltool/pvt/build/sha512/${SHA512}
sudo chmod 644 /mnt/netapp/relengweb/tooltool/pvt/build/sha512/${SHA512}
ls -l /mnt/netapp/relengweb/tooltool/pvt/build/sha512/${SHA512}
</pre>

* Add the filename, filesize, and sha512 digest to the bug you are working on. These can be added to the tooltool manifests later.

== How to upload Talos ZIPs ==
See [[ReleaseEngineering:Buildduty:Other_Duties#How_to_update_the_talos_zips|How to update the talos zips]].

== How to add NPM packages ==
See [[ReleaseEngineering/How To/Mirror NPM Packages]]

CIDuty/Other Duties

2014-04-24T19:36:21Z

Arich: /* Update mobile talos webhosts */

__TOC__

= Tree Maintenance =
== Repo Errors ==
If a dev reports a problem pushing to hg (either m-c or try repo) then you need to do the following:
* File a bug (or have dev file it) and then poke in #ops noahm
** If he doesn't respond, then escalate the bug to page on-call
* Follow the steps below for "How do I close the tree"

== How do I see problems in TBPL? ==
All "infrastructure" (that's us!) problems should be purple at http://tbpl.mozilla.org. Some aren't, so keep your eyes open in IRC, but get on any purples quickly.
== How do I close the tree? ==
See [[ReleaseEngineering/How_To/Close_or_Open_the_Tree]]

== How do I claim a rentable project branch? ==
See [[ReleaseEngineering/DisposableProjectBranches#BOOKING_SCHEDULE]]

== Clean up the scheduler DB ==
Sometimes we get some jobs pending for days:
https://secure.pub.build.mozilla.org/buildapi/pending

These are supposed to be cleaned up automatically now. See {{bug|755012}} for details.

= Re-run jobs =
== How to trigger Talos jobs ==
see [[ReleaseEngineering/How_To/Trigger_Talos_Jobs]]

== How to re-trigger all Talos runs for a build (by using sendchange) ==
see [[ReleaseEngineering/How_To/Trigger_Talos_Jobs]]

== How to re-run a build ==
Do ''not'' go to the page of the build you'd like to re-run and cook up a sendchange to try to re-create the change that caused it. Changes without revlinks trigger releases, which is not what you want.

Find the revision you want, find a builder page for the builder you want (preferably, but not necessarily, on the same master), and plug the revision, your name, and a comment into the "Force Build" form. <em>Note that the '''YOU MUST''' specify the branch, so there's no null keys in the builds-running.js.</em> Otherwise your build will not show up in self-serve or tbpl.

= Nightlies =

== How do I re-spin mozilla-central nightlies? ==
=== To rebuild the same nightly for some platform ===
buildbot's Rebuild button works fine. BUT, if the original build uploaded files or published updates you don't want to do this (caching on ftp.m.o will mean the old file is served for some time). Check the log of the original build - if it failed before uploading it's OK to rebuild.

=== To build new nightlies ===
NB: For b2g, the revision set can only be the mercurial gecko revision.

==== To build nightlies on all the platforms ====
Use [https://secure.pub.build.mozilla.org/buildapi/self-serve/mozilla-central/ self-serve] for this. Scroll to the bottom of the page and put the requested revision into the box next to ''Create new nightly builds on mozilla-central revision''. Click on the Submit button. This takes care of using the same buildID for all builds.

==== To rebuild some subset of all the nightly builders (eg only desktop/Android/b2g) ====
To reach a specific nightly builder on a build master, you can use a finished nightly job on tbpl and this snippet of javascript code (add it to the bookmark toolbar):
javascript:(function(){function%20JSONRequest(url,callback){var%20req=new%20XMLHttpRequest();req.open('GET',url+'?format=json');req.withCredentials=true;req.timeout=5000;req.onreadystatechange=function(){if(req.readyState===4){if(req.status!==200||!req.responseText){if(req.status===0){alert('Self-Serve%20API%20request%20timed%20out.');}else{alert('Self-Serve%20API%20request%20failed%20('+req.status+').%20\nIs%20the%20job%20still%20pending?%20\n\n'+req.responseText);}return;}try{callback(JSON.parse(req.responseText));}catch(e){alert(e);}}};req.send();}function%20openJob(job){var%20bm=job.claimed_by_name.split(':');var%20port=/build[0-9]/.test(bm[1])?"8001":/try[0-9]/.test(bm[1])?"8101":/tests[0-9]/.test(bm[1])?"8201":'unknown';window.open('http://'+bm[0]+':'+port+'/builders/'+job.buildername+'/builds/'+job.buildnumber);}function%20openCompletedJob(jobs){var%20selectedJob=UserInterface._activeResultObject();var%20startTime=Date.parse(selectedJob.startTime)/1000;jobs=jobs.filter(function(j){return(j.buildername===selectedJob.machine.name)&&((j.starttime-startTime)<=1);});if(jobs.length!==1){alert('Should%20have%20found%20exactly%20one%20matching%20job,%20found%20'+jobs.length+'!');return;}openJob(jobs[0]);}var%20id=(typeof%20UserInterface!=="undefined")?UserInterface._activeResult:'';if(!id){alert('Error%20-%20are%20you%20on%20TBPL%20with%20a%20job%20selected?');return;}var%20baseURL='https://secure.pub.build.mozilla.org/buildapi/self-serve/'+UserInterface.treeInfo.buildbotBranch;var%20re=/^(?:running|pending)-/;if(!re.test(id)){var%20rev=UserInterface._activeResultObject().revs[UserInterface.treeInfo.primaryRepo];JSONRequest(baseURL+'/rev/'+rev,openCompletedJob);}else{JSONRequest(baseURL+'/build/'+id.replace(re,''),openJob);}})()

You will need to force the specific builders on a build master, setting several parameters. First open a waterfall page (eg [http://buildbot-master82.build.mozilla.org:8001/waterfall?category=mozilla-central&num_events=0 mozilla-central]) and search for 'nightly'. Open each builder you want in a new tab.

For each builder you should set
* 'Your name' to your name
* 'Reason for build' to 'bug ###' or 'requested by <someone>'
* 'Branch to build' to 'mozilla-central' (other branches may have a prefix, eg releases/mozilla-aurora)
* 'Revision to build' to the <revision>
* 'Property 1': 'Name' to 'buildid', 'Value' to the current Pacific time (eg from running <tt>TZ=US/Pacific date +%Y%m%d%H%M%S</tt>)
Then click on the 'Force build' button.

The first two are nice-to-have for later debugging. The branch and revisions are required so that TBPL shows the builds while they are pending and running (rather than just after completion). Setting the buildid property the same across all builds helps keep nightlies consistent. An add-on like [https://addons.mozilla.org/en-US/firefox/addon/autofill-forms/ AutoFill Forms] is invaluable in storing these values and filling the form for you, but there is probably a way to do this with curl too (it's a POST).

== Disable updates ==

See [[ReleaseEngineering/How_To/Shut_off_all_updates]] for global shutoff. We use Balrog now for nightly & aurora updates.

= Talos =
== How to update the talos zips ==
We only need to do this for mobile requests.

'''This deployment is super safe. NPOTB'''

<pre>
# running this from cruncher is faster than downloading/uploading from your localhost
ssh -A cruncher
export URL=http://people.mozilla.org/~jmaher/taloszips/zips/talos.07322bbe0f7d.zip
export TALOS_ZIP=`basename $URL`
wget $URL
#relengwebadmn has limited access to the internet - that is why we scp from another host
scp ${TALOS_ZIP} relengwebadm.private.scl3.mozilla.com:/mnt/netapp/relengweb/talos-bundles/zips
ssh relengwebadm.private.scl3.mozilla.com "chmod 644 /mnt/netapp/relengweb/talos-bundles/zips/${TALOS_ZIP}"
ssh relengwebadm.private.scl3.mozilla.com "sha1sum /mnt/netapp/relengweb/talos-bundles/zips/${TALOS_ZIP}"
curl -I http://talos-bundles.pvt.build.mozilla.org/zips/${TALOS_ZIP}
</pre>

For talos.zip changes: Once deployed, notify the a-team and let them know that they can land at their own convenience.

== Update mobile talos webhosts ==

Keep track of what revisions is being run.
Copy/paste the output into the bug.
Please update our [[ReleaseEngineering/Maintenance#Mobile_talos_webhost|maintenance page]]

'''This could affect mobile talos numbers or break the jobs altogether. Please coordinate with sheriffs'''

'''NOTE: There's a great deal of data we can not check into revision control for legal reasons, so there's an extensive .hgignore file. If you're adding new data to the tree that can not be checked in, please make sure to add it to the .hgignore file as well so that people are not confused by files when they perform an hg status'''

'''NOTE: For now, we're only using the "old, mac mini" setup. Update both but only talk about the old setup'''

=== new, webapp cluster ===

ssh relengwebadm.private.scl3.mozilla.com
sudo su -
cd /data/releng/src/talos-remote/www/talos-repo
# NOTICE that we have uncommitted files
hg status
# Take note of the current revision to revert to (just in case)
hg id
hg pull -u
# 488bc187a3ef tip
# ..capture the output here; the remainder will be long and not that useful..
/data/releng/src/talos-remote/update

=== old, mac mini ===
We have a load balancer (bm-remote) that is in front of three web hosts (bm-remote-talos-0{1,2,3}). Here is how you update them: Update Procedure:

ssh root@bm-remote-talos-webhost-01
cd /var/www/html/talos-repo
# NOTICE that we have uncommitted files
hg status
# Take note of the current revision to revert to (just in case)
hg id
hg pull -u
# 488bc187a3ef tip
rsync -azv --delete /var/www/html/. bm-remote-talos-webhost-02:/var/www/html/.
rsync -azv --delete /var/www/html/. bm-remote-talos-webhost-03:/var/www/html/.

= TBPL =
== How to deploy changes ==
RelEng no longer has access to do this. TBPL devs will request a push from Server Ops.

== How to hide/unhide builders ==
* In the 'Tree Info' menu select 'Open tree admin panel'
* Filter/select the builders you want to change
* Save changes
* Enter the sheriff password and a description (with bug number if available) of your changes
* CC :edmorley & :philor on the relevant bug so that they know what to expect when sheriffing.

= Ganglia =
* if you see that a host is reporting to ganglia in an incorrect manner it might just take this to fix it (e.g. {{bug|674233}}):
switch to root, service gmond restart

= Queue Directories =
* [https://wiki.mozilla.org/ReleaseEngineering/Queue_directories Queue directories]

If you see this in #build:

<nagios-sjc1> [54] buildbot-master12.build.scl1:Command Queue is CRITICAL: 4 dead items

It means that there are items in the "dead" queue for the given master. You need to look at the logs and fix any underlying issue and then retry the command by moving *only* the json file over to the "new" queue. See the [https://wiki.mozilla.org/ReleaseEngineering/Queue_directories Queue directories] wiki page for details.
= Cruncher =
If you get an alert about cruncher running out of space it might be a sendmail issue (backed up emails taking up too much space and not getting sent out):

<nagios-sjc1> [07] cruncher.build.sjc1:disk - / is WARNING: DISK WARNING - free space: / 384 MB (5% inode=93%):
As root:
du -s -h /var/spool/*
# confirm that mqueue or clientmqueue is the oversized culprit
# stop sendmail, clean out the queues, restart sendmail
/etc/init.d/sendmail stop
rm -rf /var/spool/clientmqueue/*
rm -rf /var/spool/mqueue/*
/etc/init.d/sendmail start

= hg<->git conversion =
This is a production system RelEng built, but has not yet transitioned to full IT operation. As a production system, it is supported 24x7x365 - escalate to IT oncall (who can page) as needed.

We'll get problem reports from 2 sources:
* via email from vcs2vcs user to release+vcs2vcs@m.c - see [[ReleaseEngineering/How_To/Process_release_email|email handling]] instructions for those.
* via a bug report for a customer visible condition - this should only be if there is a new error we aren't detecting ourselves. See the resources below and/or page hwine.

Documentation for this system:
* [http://people.mozilla.com/~hwine/tmp/vcs2vcs/ recent docs] ([http://people.mozilla.org/~hwine/tmp/vcs2vcs/trouble_shooting.html troubleshooting])
* source code: http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/
* config files: http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/

All services run as user vcs2vcs on one of the following hosts (as of 2013-01-07): github-sync1-dev.dmz.scl3.mozilla.com, github-sync1.dmz.scl3.mozilla.com, github-sync2.dmz.scl3.mozilla.com, github-sync3.dmz.scl3.mozilla.com.

== Handling alert_major_errors ==

# SSH as yourself to the hostname in the 'from' address of the alert_major_errors email.
$ ssh yourname@github-sync3.dmz.scl3.mozilla.com
$ sudo su - vcs2vcs
$ cd etc
# find the repo name that vcs2vcs is complaining about. For example:
$ grep releases-mozilla-central-no-cvs *
job02_cmds:# "hg:$HOME/repos/releases-mozilla-central-no-cvs" "github"
# discover where that job runs
$ grep job02 status
job02_cmds,github-sync3.dmz.scl3.mozilla.com,m-c w/o cvs as used by b2g
# connect to that host the same as we did above (if not already connected)
# then
$ cd logs/job02 # same job as above
$ show_update_errors update.log
# Note: the command exit code precedes the command itself
# eg. ...;255;hg --cwd...

Continue with instructions [http://people.mozilla.com/~hwine/tmp/vcs2vcs/trouble_shooting.html#repo-copy-not-updating here].

= disable/re-enable aurora updates =
Take care of by the person doing the final release since merge day activities are on the Monday before the release.

= Upload =
== Python packages ==
{{warning|Mozharness no longer uses packages from the PuppetAgain repositories! Instead, it uses http://pypi.pub.build.mozilla.org/pub and http://pypi.pvt.build.mozilla.org/pub, both served from the same directory.}}
From your local machine:
FILE=your_python_package.tar.gz
scp $FILE $LDAP_SHORT_USERNAME@relengwebadm.private.scl3.mozilla.com:
From relengwebadm:
ssh $LDAP_SHORT_USERNAME@relengwebadm.private.scl3.mozilla.com

FILE=your_python_package.tar.gz
sudo mv -vi $FILE /mnt/netapp/relengweb/pypi/pub/
sudo chmod 644 /mnt/netapp/relengweb/pypi/pub/$FILE

From your local machine:
curl -I http://pypi.pub.build.mozilla.org/pub/$FILE
# You should see "HTTP/1.1 200 OK"

== How to upload to Tooltool ==
If you don't want to upload from your own laptop (because, eg, you have a slow uplink) you can do this from cruncher.

Access cruncher with your credentials:
ME="your_short_ldap_username" # or `whoami`
ssh -A $ME@cruncher.build.mozilla.org
Download the file and then:
scp filename.tar.xz $ME@relengwebadm.private.scl3.mozilla.com:
Login to relengwebadmn:
ssh $ME@relengwebadm.private.scl3.mozilla.com
And deploy the file to tooltool:
<pre>
FILE=~/emulator.zip # or whatever you're uploading
export SHA512=`openssl sha512 $FILE | cut -d' ' -f2`
sudo mv -i $FILE /mnt/netapp/relengweb/tooltool/pvt/build/sha512/${SHA512}
sudo chmod 644 /mnt/netapp/relengweb/tooltool/pvt/build/sha512/${SHA512}
ls -l /mnt/netapp/relengweb/tooltool/pvt/build/sha512/${SHA512}
</pre>

* Add the filename, filesize, and sha512 digest to the bug you are working on. These can be added to the tooltool manifests later.

== How to upload Talos ZIPs ==
See [[ReleaseEngineering:Buildduty:Other_Duties#How_to_update_the_talos_zips|How to update the talos zips]].

== How to add NPM packages ==
See [[ReleaseEngineering/How To/Mirror NPM Packages]]

Platform/2014-Q2-Goals

2014-04-21T19:26:20Z

Arich: /* Release Engineering Operations */

Platform/2014-Q2-Goals

2014-04-21T19:23:20Z

Arich: /* Release Engineering Operations */

Platform/2014-Q2-Goals

2014-04-21T19:19:35Z

Arich: /* Release Engineering Operations */

Platform/2014-Q2-Goals

2014-04-21T17:09:58Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
=== Layout ===

* {{ok|Table Rendering with DisplayLists}}

* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Vertical text: Implement Layout frame migration to logical coordinates https://etherpad.mozilla.org/css-writing-modes
** {{ok|convert cross-layout classes}}

* Text Performance bugs ( https://etherpad.mozilla.org/textperfworkitems )
** {{ok|large text frames / interruptible reflow}}
** {{ok|enumerated font list fixes}}

* Improve Restyling Performance
** {{ok|bug 977991, and maybe bugs 804975/977594}}

* GFx work items
** {{ok|E10S BasicCompositor}}
** {{ok|GFx tiling}}
** {{ok|Accelerated Filters}}
*** spec work
*** shader & support work

* CSS Flexbox
** {{ok|pagination}}
** recently-finalized spec changes (abspos, min-width, flex sizing) (874718, 984711, 985304)

* Animations & Transitions
** {{ok|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{ok|test_animations covering OMTA}}
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{ok|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|Spec an API for querying basic properties of running CSS animations/transitions}}

* Ship and/or unprefix:
** {{ok|position:sticky}}
** {{ok|Font-features that need fallback support (eg. small-caps)}}

* 3D Transforms
** interop bugs and spec improvement (bug 976365)
** implement preserve-3d proposal
** perf work

* Font Inflation and Reflow-on-Zoom
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* CSS Projects with Adobe
** {{ok|CSS Filters}}
** {{ok|CSS Masking}}
** {{ok|CSS Compositing}}

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Fonts
** {{ok|font load events}}

=== Media ===
=== DOM ===
* {{ok|Implement Xrays to 3 out of the following: Functions ({{bug|976148}}), Objects ({{bug|987111}}), Array/Array-like ({{bug|987163}}), and Error ({{bug|987669}})}}
* {{ok|Get rid of the long tail of C++ objects that are still exposed to the web using XPConnect}}
* {{ok|Get LeakSanitizer builds enabled by default ({{bug|988041}})}}
* {{ok|Identify and fix (DOM stuff, at least) hotspots in b2g app startup (smaug)}}
* {{ok|refactor how tokenizer and tree builder use buffers to reduce memory pressure crashes (hsivonen)}}
* {{ok|Land all non-cache bits of Service Workers preffed-off (on is a bonus) on m-c (nsm)}}
* {{ok|Help guide and review requestAutocomplete backend implementation ({{bug|939351}})}} (likely smaug)
* {{prev|implement [http://picture.responsiveimages.org/ <picture>] ({{bug|870022}}) (johns)}}
* {{ok|Ensure plugins are shippable for e10s}} (johns)

=== WebAPI ===
* {{ok|finalize moving main thread IDB to PBackground including blobs}} (bent)
* {{ok|Convert DataStore cursors and DataStore object itself from JS to C++ (baku)}}
* {{ok|Finalize moving quotamanager to PBackground}} (janv)
* {{ok|clarify design and spec issues around Fetch for Service Workers to ensure they're implementable}} (annevk)
* {{ok|implement gecko side of [http://w3c.github.io/manifest/ manifest] spec}} ({{bug|997779}}) (marcosc)
* {{ok|finish [https://w3c.github.io/screen-orientation/ device orientation] spec with Mounir}} (marcosc)

=== JS ===
=== Accessibility ===
* {{ok|Sandboxing support: create and update cached structure of the accessible tree in the parent process (tbsaunde)}}
* {{prev|Windows support: Land basic UIA text navigation implementation (surkov)}}
* {{ok|FFOS/GAIA: under construction (eeejay,marcoz,yzen)}}
Note nicks indicate DRI(s) and all work is collaborative.

=== Perf ===

* Improve Firefox responsiveness & startup time:
** Finish session-store work:
*** {{ok|Improve session-store startup time {{bug|987592}} }}
*** {{ok|Store less data in the sessionstore.js file {{bug|943352}} }}
*** {{ok|Break up janky operations into smaller chunks {{bug|984886}} }}
** Start eliminating top main-thread I/O offenders reported to Telemetry {{bug|572459}}:
*** 1. {{ok|User dictionary (persdict.dat) read on the main thread {{bug|880864}} }}
*** 2. TBD
** {{ok|New storage system for prefs {{bug|897049}} }}
** {{ok|The add-on compatibility dialog should not interrupt startup unless strictly necessary {{bug|760356}} }}
** {{ok|Investigate feasibility of starting Flash plugin instances asynchronously}}

* Fill gaps in test coverage (vs press benchmarks) and prevent regressions:
** {{ok|Create a Talos test for "cold" startup time {{bug|936617}} }}
** {{ok|Create a Talos test for time to restore a previous session {{bug|936630}} }}
** {{ok|Integrate our new power-profiling test into the test infrastructure {{bug|962715}} }}
** {{ok|Automatically detect new sources of main-thread I/O in tests {{bug|935482}} }}
** {{ok|Monitor & track regressions in important Talos tests during each release cycle}}

* Partner with other teams on projects with big perf impact
** {{ok|Assist Necko team with measuring performance of new network cache}}
** {{ok|Make it easier to debug performance regressions by (optionally) capturing profiles during Talos tests {{bug|967619}} }}
** {{ok|Expand use of the T100 tablet/laptop as a reference slow device}}
** {{ok|Work with fx-team on ongoing regressions}}
** {{ok|Add performance tests for OMTC/APZC}}

* Study impact of extensions on Firefox performance
** {{ok|Create a Telemetry dashboard to expose add-ons' impact on Firefox startup time}}

* Grow community:
** {{ok|Mentor at least 5 new external contributors}}

=== Networking ===

* {{ok|Mitigate CSRF attacks against internal networks (block rfc 1918 local addresses from non-local addresses) ({{bug|354493}}) (sworkman) }}
* {{ok|HTTP/2: implement draft-11 of HTTP/2 spec and continue participating in spec development. (hurley / mcmanus) }}
* {{ok|Turn on new HTTP cache in nightly (honza / michal) }}
* {{ok| NetworkLinkService should be enabled so Necko can respond to network changes ({{bug|939318}}) (bagder) }}
* {{ok|B2G: Provide way to "set network offline" per app ({{bug|786419}}) (valentin) }}
* {{ok|Gather data and produce a report on performance wins vs resource costs of the seer on several desktop and mobile scenarios. (hurley) }}

=== Mobile ===
=== A*Team ===
full list: [[Auto-tools/Goals/2014Q2]]

* B2G
** {{ok|}} Deliver v2 of the FxOS Certification Suite
** {{ok|}} Build a common harness for Python and NodeJS Marionette tests, and enable them to run on devices and emulators

* Performance
** {{ok|}} Deploy a Talos dashboard that will allow Talos regressions to be more easily "sheriffed"
** {{ok|}} Improve Eideticker's ability to scale
** {{ok|}} Prototype Datazilla alerts for Talos and Eideticker data

* Mobile
** {{ok|}} Move Android 2.3 reftests off of tegras
** {{ok|}} Designate autophone and/or Eideticker as official perf systems for Android 2.3

* Bugzilla
** {{ok|}} Migrate BMO and upstream Bugzilla CI from Tinderbox to travis-ci.
** {{ok|}} Continue and deepen analysis of BMO perf data.
** {{ok|}} Determine list of possible improvements, estimate gains, prioritize, and implement.

* Treeherder
** {{ok|}} Deploy a production version of Treeherder in coordination with Laura's team
** {{ok|}} Define and implement a sheriff transition plan to move from TBPL to Treeherder
** {{ok|}} Have Treeherder report data to OrangeFactor

* Community
** {{ok|}} Refresh our list of "good first bugs" on a monthly basis
** {{ok|}} Review these and make sure they have adequate information for contributors to start with
** {{ok|}} Keep the numbers of open good first bugs steady or increasing

=== Web Engineering ===
* crash-stats
** {{ok|}} Prototype work to support 100% crash processing for support classification and better user retention after a crash [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Implement symbol upload by partners [Scale FirefoxOS]
** {{ok|}} Better search, graphs, and correlation reports to support QA and Crashkill teams [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Infrastructure improvements to support shipping engineer-requested features faster [Get Firefox on a Growth Trajectory / Scale FxOS]

* FHR
** {{ok|}} Research and develop a plan for addressing sideloading [Invest in Sustainability]

* DXR
** {{ok|}} Move to a more scalable data store to enable indexing all trees [Scale FxOS]
** {{ok|}} Implement search result mixing [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Improve documentation and install to lower the bar for contribution [Enable Communities with Impact]

* l10n
** {{ok|}} (stretch) Remove dependency on buildbot [Enable Communities with Impact]

* Plugincheck
** {{ok|}} Ship new version to support Firefox 29+ [Get Firefox on a Growth Trajectory]

* Air Mozilla
** {{ok|}} Open event editing to all signed in users, wiki style [Enable Communities with Impact]
** {{ok|}} Protoype ability to search by transcript [Enable Communities with Impact]

[https://etherpad.mozilla.org/webeng-q22014 Full list]

=== SUMO and Input ===
* SUMO
** {{ok|}} Implement interactive onboarding for new community volunteers [Enable communities with impact]
** {{ok|}} Implement an initial community hub [Enable communities with impact]
** {{ok|}} Prototype BuddyUp app: interactive support for FirefoxOS [Scale FirefoxOS]

* Input
** {{ok|}} Integrate with Gengo translation API to improve localization [Enable communities with impact]
** {{ok|}} (stretch) Implement and roll out new product-centric dashboards [Scale FirefoxOS]

[https://etherpad.mozilla.org/sumodev-2014-goals Full list]

=== Release Engineering ===
* {{ok|}} Plan and implement a sustainable approach to releases on legacy Android platforms [Get Firefox on a Growth Trajectory]
* {{ok|}} Support infrastructure work on closing scl3 datacenter to save cost [Get Firefox on a Growth Trajectory]
* {{ok|}} Implement automation (slave loan tool) to reduce manual work [Get Firefox on a Growth Trajectory]
* {{ok|}} Stand up device builds for b2g reference phones [Scale FirefoxOS]
* {{ok|}} Remove dependencies on and turn off deprecated systems [Get Firefox on a Growth Trajectory]
* {{ok|}} Audit monitoring and instrumentation of release systems with a view to getting better insight, enabling better agility [Scale FirefoxOS]
* {{ok|}} Continue Balrog (new AUS) rollout to beta, and prepare for release/ESR [Get Firefox on a Growth Trajectory]
* {{ok|}} Automate merge day processes [Get Firefox on a Growth Trajectory]
* Continue infrastructure improvement program:
** {{ok|}} Move more work into the cloud to reduce cost and increase agility [Scale FirefoxOS]
** {{ok|}} Improve build and test environment for Windows [Get Firefox on a Growth Trajectory]
** {{ok|}} Get taskcluster ready to replace buildbot in Q3 and Q3 [Scale FirefoxOS]
* Joint goals with A-team:
** {{ok|}} Design an API that will be the single source of truth about release information [Get Firefox on a Growth Trajectory

[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Ajlqy6z1WDBvdGNxaFFpbnQ4UDdySzZVcGU1RkN4b0E&usp=sharing&pli=1#gid=10 Full list]

=== Release Engineering Operations ===

* Datacenter Consolidation
** {{ok| (Cost reduction) Migrate SCL1 infrastructure to SCL3 and close SCL1 datacenter. {{bug|981124}} }}
** {{ok| (Cost reduction) Decommission deprecated hardware. {{bug|997213}} and {{bug| 961164}} }}

* Build/Test System Performance Enhancements
** {{ok| (Get Firefox on a trajectory of growth) Create a POC for Windows build systems on seamicro/SSD hardware and replicate to replace most of the existing Windows build infrastructure if successful. {{bug|982261}} }}
** {{ok| (Get Firefox on a trajectory of growth) Create a POC for OS X build systems using SSD drives and replicate to the rest of the existing OS X build infrastructure if successful. {{bug|992364}} }}
** {{ok| (Get Firefox on a trajectory of growth) Architect and deploy a 3-node Ceph Prototype instance if tests on the existing POC show significant build speed increases. {{bug|995512}} }}

* Build/Test System Self-Serve Re-architecture
** {{ok| (Get Firefox on a trajectory of growth) Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} }}
** {{ok| (Get Firefox on a trajectory of growth) Develop a new image creation solution for 2008R2 build machines which can be used to deploy on bare metal. {{bug|798657}} }}

[https://etherpad.mozilla.org/relops-q22014 Full list]

=== Developer Services ===
* {{ok|}} Review and scale out git architecture [Scale FirefoxOS]
* {{ok|}} (with B-team) Improve performance and review tools for Bugzilla [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{ok|}} (with A-team) Deploy better tree visualization tools [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{ok|}} Plan and prototype future release engineering architecture [Get Firefox on a Growth Trajectory / Scale FirefoxOS]

[https://etherpad.mozilla.org/devservices-Q22014 Full list]

=== Security & Privacy ===
Full list here: [[SecurityEngineering/2014/Q2Goals]]

* Web Platform Security
** {{new|plan out replacement for nsIContentPolicy and start executing}} (dri=tanvi, +sicking,ckerschb)
** {{ok|Make new CSP parser on by default in nightly}} (dri=ckerschb, +grobinson,sstamm)
** {{ok|Land WebCrypto}} (dri=rbarnes) {{Bug|865789}}
* Secure Client Platform
** {{new|Get open.h264 plugin sandboxed on windows}} [dri=sstamm, a=tabraldes]
** {{prev|something about sandboxing logging}} [dri=bobowen, a=sstamm,tabraldes]
* Secure Communications
** {{prev|Land key pinning}} [dri=cviecco, a=keeler,mmc]
** {{new|mozilla::pkix on by default, (riding the train to) / (targeting a) release}} [dri=keeler, a=cviecco]
** {{new| BONUS: Deploy UI for cert error reporting}} [dri=kathleen]
* Tracking Protection / Privacy
** {{ok|Get through the [https://github.com/mozilla/lightbeam/issues/milestones next 2 releases] of Lightbeam}} [dri=mmc, a=grobinson]

ReleaseEngineering/PuppetAgain/HowTo/Set up a user environment

2014-04-17T20:42:21Z

Arich: /* Common */

Approved people have SSH logins on all puppet masters and a puppet environment at /etc/puppet/environments/$username/env.

You can use this environment to do your development.

= Common =

In general, you'll want to clone http://hg.mozilla.org/build/puppet at /etc/puppet/environments/$USER/env (not in a subdirectory). You can use git if you'd like. Then:

cd /etc/puppet/environments/$USER/env/manifests
ln -s moco-config.pp config.pp
ln -s moco-nodes.pp nodes.pp

Next, you can run puppet agent on a client and tell it to use your environment on the server you've selected:

$ su -
# puppet agent --test --environment=dmitchell --server=releng-puppet2.srv.releng.scl3.mozilla.com

On a mac slave, on the first run you will have to specify the ssl dir. For example:

$ su -
# puppet agent --test --server=releng-puppet2.srv.releng.scl3.mozilla.com --environment=kmoir --pluginsync --ssldir=/var/lib/puppet/ssl

Note that this command will use the nearest puppet master. You can add --server=.. to specify a different puppet master.

== Secrets ==

Note that your secrets will come from the same Hiera datasource as everything else. You can override secrets for your env only in <tt>/etc/hiera/environments/<yourname>_secrets.eyaml</tt>.

= Problems =

The most common problem that you'll see is that your version control system will helpfully make the files in your repository not world-readable, and in particular preclude puppet from reading them.

This will result in this error message when try to run puppet on your slave
"Could not parse for environment $yourid: Permission denied"
in /etc/puppet/environments/$yourid

find . -type f | xargs chmod o+r
find . -type d | xargs chmod o+rx

This ''should'' not be a problem anymore - puppet is now a member of each user's group, so it should be able to read the repository with the 'g' permissions. Please file bugs or contact dustin for any permissions problems.

= Pinning =

If you want to make a node use your environment on every run (e.g., for slaves that run puppet at boot), you can "pin" the host to your environment. Edit the node definition like this:
node "hostname" {
# the pins must come *before* the toplevel include
$pin_puppet_server = "releng-puppet2.build.scl1.mozilla.com"
$pin_puppet_env = "dmitchell"
include toplevel::slave::build
}

This will result in a puppet.conf on the client that specifies the server and environment.

= Git =

If you're using git, set things up as follows:

cd env
git init

edit .git/config, and add

sharedRepository = 0644

to the [core] section. Then clone a copy of the git repository (e.g., from http://github.com/djmitche/releng-puppet), and start hacking.

Platform/2014-Q2-Goals

2014-04-17T14:39:27Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
=== Layout ===

* {{ok|Table Rendering with DisplayLists}}

* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Vertical text: Implement Layout frame migration to logical coordinates https://etherpad.mozilla.org/css-writing-modes
** {{ok|convert cross-layout classes}}

* Text Performance bugs ( https://etherpad.mozilla.org/textperfworkitems )
** {{ok|large text frames / interruptible reflow}}
** {{ok|enumerated font list fixes}}

* Improve Restyling Performance
** {{ok|bug 977991, and maybe bugs 804975/977594}}

* GFx work items
** {{ok|E10S BasicCompositor}}
** {{ok|GFx tiling}}
** {{ok|Accelerated Filters}}
*** spec work
*** shader & support work

* CSS Flexbox
** {{ok|pagination}}
** recently-finalized spec changes (abspos, min-width, flex sizing) (874718, 984711, 985304)

* Animations & Transitions
** {{ok|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{ok|test_animations covering OMTA}}
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{ok|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|Spec an API for querying basic properties of running CSS animations/transitions}}

* Ship and/or unprefix:
** {{ok|position:sticky}}
** {{ok|Font-features that need fallback support (eg. small-caps)}}

* 3D Transforms
** interop bugs and spec improvement (bug 976365)
** implement preserve-3d proposal
** perf work

* Font Inflation and Reflow-on-Zoom
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* CSS Projects with Adobe
** {{ok|CSS Filters}}
** {{ok|CSS Masking}}
** {{ok|CSS Compositing}}

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Fonts
** {{ok|font load events}}

=== Media ===
=== DOM ===
* {{ok|Implement Xrays to 3 out of the following: Functions ({{bug|976148}}), Objects ({{bug|987111}}), Array/Array-like ({{bug|987163}}), and Error ({{bug|987669}})}}
* {{ok|Get rid of the long tail of C++ objects that are still exposed to the web using XPConnect}}
* {{ok|Get LeakSanitizer builds enabled by default ({{bug|988041}})}}
* {{ok|Identify and fix (DOM stuff, at least) hotspots in b2g app startup (smaug)}}
* {{ok|refactor how tokenizer and tree builder use buffers to reduce memory pressure crashes (hsivonen)}}
* {{ok|Land all non-cache bits of Service Workers preffed-off (on is a bonus) on m-c (nsm)}}
* {{ok|Help guide and review requestAutocomplete backend implementation ({{bug|939351}})}} (likely smaug)

=== WebAPI ===
* {{ok|finalize moving main thread IDB to PBackground including blobs}} (bent)
* {{ok|Convert DataStore cursors and DataStore object itself from JS to C++ (baku)}}
* {{ok|Finalize moving quotamanager to PBackground}} (janv)
* {{ok|clarify design and spec issues around Fetch for Service Workers to ensure they're implementable}} (annevk)

=== JS ===
=== Accessibility ===
* {{ok|Sandboxing support: create and update cached structure of the accessible tree in the parent process (tbsaunde)}}
* {{prev|Windows support: Land basic UIA text navigation implementation (surkov)}}
* {{ok|FFOS/GAIA: under construction (eeejay,marcoz,yzen)}}
Note nicks indicate DRI(s) and all work is collaborative.

=== Perf ===

* Improve Firefox responsiveness & startup time:
** Finish session-store work:
*** {{ok|Improve session-store startup time {{bug|987592}} }}
*** {{ok|Store less data in the sessionstore.js file {{bug|943352}} }}
*** {{ok|Break up janky operations into smaller chunks {{bug|984886}} }}
** Start eliminating top main-thread I/O offenders reported to Telemetry {{bug|572459}}:
*** 1. {{ok|User dictionary (persdict.dat) read on the main thread {{bug|880864}} }}
*** 2. TBD
** {{ok|New storage system for prefs {{bug|897049}} }}
** {{ok|The add-on compatibility dialog should not interrupt startup unless strictly necessary {{bug|760356}} }}
** {{ok|Investigate feasibility of starting Flash plugin instances asynchronously}}

* Fill gaps in test coverage (vs press benchmarks) and prevent regressions:
** {{ok|Create a Talos test for "cold" startup time {{bug|936617}} }}
** {{ok|Create a Talos test for time to restore a previous session {{bug|936630}} }}
** {{ok|Integrate our new power-profiling test into the test infrastructure {{bug|962715}} }}
** {{ok|Automatically detect new sources of main-thread I/O in tests {{bug|935482}} }}
** {{ok|Monitor & track regressions in important Talos tests during each release cycle}}

* Partner with other teams on projects with big perf impact
** {{ok|Assist Necko team with measuring performance of new network cache}}
** {{ok|Make it easier to debug performance regressions by (optionally) capturing profiles during Talos tests {{bug|967619}} }}
** {{ok|Expand use of the T100 tablet/laptop as a reference slow device}}
** {{ok|Work with fx-team on ongoing regressions}}
** {{ok|Add performance tests for OMTC/APZC}}

* Study impact of extensions on Firefox performance
** {{ok|Create a Telemetry dashboard to expose add-ons' impact on Firefox startup time}}

* Grow community:
** {{ok|Mentor at least 5 new external contributors}}

=== Networking ===

* {{ok|Mitigate CSRF attacks against internal networks (block rfc 1918 local addresses from non-local addresses) ({{bug|354493}}) (sworkman) }}
* {{ok|HTTP/2: implement draft-11 of HTTP/2 spec and continue participating in spec development. (hurley / mcmanus) }}
* {{ok|Turn on new HTTP cache in nightly (honza / michal) }}
* {{ok| NetworkLinkService should be enabled so Necko can respond to network changes ({{bug|939318}}) (bagder) }}
* {{ok|B2G: Provide way to "set network offline" per app ({{bug|786419}}) (valentin) }}
* {{ok|Gather data and produce a report on performance wins vs resource costs of the seer on several desktop and mobile scenarios. (hurley) }}

=== Mobile ===
=== A*Team ===
full list: [[Auto-tools/Goals/2014Q2]]

* B2G
** {{ok|}} Deliver v2 of the FxOS Certification Suite
** {{ok|}} Build a common harness for Python and NodeJS Marionette tests, and enable them to run on devices and emulators

* Performance
** {{ok|}} Deploy a Talos dashboard that will allow Talos regressions to be more easily "sheriffed"
** {{ok|}} Improve Eideticker's ability to scale
** {{ok|}} Prototype Datazilla alerts for Talos and Eideticker data

* Mobile
** {{ok|}} Move Android 2.3 reftests off of tegras
** {{ok|}} Designate autophone and/or Eideticker as official perf systems for Android 2.3

* Bugzilla
** {{ok|}} Migrate BMO and upstream Bugzilla CI from Tinderbox to travis-ci.
** {{ok|}} Continue and deepen analysis of BMO perf data.
** {{ok|}} Determine list of possible improvements, estimate gains, prioritize, and implement.

* Treeherder
** {{ok|}} Deploy a production version of Treeherder in coordination with Laura's team
** {{ok|}} Define and implement a sheriff transition plan to move from TBPL to Treeherder
** {{ok|}} Have Treeherder report data to OrangeFactor

* Community
** {{ok|}} Refresh our list of "good first bugs" on a monthly basis
** {{ok|}} Review these and make sure they have adequate information for contributors to start with
** {{ok|}} Keep the numbers of open good first bugs steady or increasing

=== Web Engineering ===
* crash-stats
** {{ok|}} Prototype work to support 100% crash processing for support classification and better user retention after a crash [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Implement symbol upload by partners [Scale FirefoxOS]
** {{ok|}} Better search, graphs, and correlation reports to support QA and Crashkill teams [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Infrastructure improvements to support shipping engineer-requested features faster [Get Firefox on a Growth Trajectory / Scale FxOS]

* FHR
** {{ok|}} Research and develop a plan for addressing sideloading [Invest in Sustainability]

* DXR
** {{ok|}} Move to a more scalable data store to enable indexing all trees [Scale FxOS]
** {{ok|}} Implement search result mixing [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Improve documentation and install to lower the bar for contribution [Enable Communities with Impact]

* l10n
** {{ok|}} (stretch) Remove dependency on buildbot [Enable Communities with Impact]

* Plugincheck
** {{ok|}} Ship new version to support Firefox 29+ [Get Firefox on a Growth Trajectory]

* Air Mozilla
** {{ok|}} Open event editing to all signed in users, wiki style [Enable Communities with Impact]
** {{ok|}} Protoype ability to search by transcript [Enable Communities with Impact]

[https://etherpad.mozilla.org/webeng-q22014 Full list]

=== SUMO and Input ===
* SUMO
** {{ok|}} Implement interactive onboarding for new community volunteers [Enable communities with impact]
** {{ok|}} Implement an initial community hub [Enable communities with impact]
** {{ok|}} Prototype BuddyUp app: interactive support for FirefoxOS [Scale FirefoxOS]

* Input
** {{ok|}} Integrate with Gengo translation API to improve localization [Enable communities with impact]
** {{ok|}} (stretch) Implement and roll out new product-centric dashboards [Scale FirefoxOS]

[https://etherpad.mozilla.org/sumodev-2014-goals Full list]

=== Release Engineering ===
* {{ok|}} Plan and implement a sustainable approach to releases on legacy Android platforms [Get Firefox on a Growth Trajectory]
* {{ok|}} Support infrastructure work on closing scl3 datacenter to save cost [Get Firefox on a Growth Trajectory]
* {{ok|}} Implement automation (slave loan tool) to reduce manual work [Get Firefox on a Growth Trajectory]
* {{ok|}} Stand up device builds for b2g reference phones [Scale FirefoxOS]
* {{ok|}} Remove dependencies on and turn off deprecated systems [Get Firefox on a Growth Trajectory]
* {{ok|}} Audit monitoring and instrumentation of release systems with a view to getting better insight, enabling better agility [Scale FirefoxOS]
* {{ok|}} Continue Balrog (new AUS) rollout to beta, and prepare for release/ESR [Get Firefox on a Growth Trajectory]
* {{ok|}} Automate merge day processes [Get Firefox on a Growth Trajectory]
* Continue infrastructure improvement program:
** {{ok|}} Move more work into the cloud to reduce cost and increase agility [Scale FirefoxOS]
** {{ok|}} Improve build and test environment for Windows [Get Firefox on a Growth Trajectory]
** {{ok|}} Get taskcluster ready to replace buildbot in Q3 and Q3 [Scale FirefoxOS]
* Joint goals with A-team:
** {{ok|}} Design an API that will be the single source of truth about release information [Get Firefox on a Growth Trajectory

[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Ajlqy6z1WDBvdGNxaFFpbnQ4UDdySzZVcGU1RkN4b0E&usp=sharing&pli=1#gid=10 Full list]

=== Release Engineering Operations ===

* Datacenter Consolidation
** {{ok| (Cost reduction) Migrate SCL1 infrastructure to SCL3 and close SCL1 datacenter. {{bug|981124}} }}
** {{ok| (Cost reduction) Decommission deprecated hardware. {{bug|997213}} and {{bug| 961164}} }}

* Build/Test System Performance Enhancements
** {{ok| (Scale Firefox) Create a POC for Windows build systems on seamicro/SSD hardware and replicate to replace most of the existing Windows build infrastructure if successful. {{bug|982261}} }}
** {{ok| (Scale Firefox) Create a POC for OS X build systems using SSD drives and replicate to the rest of the existing OS X build infrastructure if successful. {{bug|992364}} }}
** {{ok| (Scale Firefox) Architect and deploy a 3-node Ceph Prototype instance if tests on the existing POC show significant build speed increases. {{bug|995512}} }}

* Build/Test System Self-Serve Re-architecture
** {{ok| (Scale Firefox) Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} }}
** {{ok| (Scale Firefox) Develop a new image creation solution for 2008R2 build machines which can be used to deploy on bare metal. {{bug|798657}} }}

[https://etherpad.mozilla.org/relops-q22014 Full list]

=== Developer Services ===
* {{ok|}} Review and scale out git architecture [Scale FirefoxOS]
* {{ok|}} (with B-team) Improve performance and review tools for Bugzilla [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{ok|}} (with A-team) Deploy better tree visualization tools [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{ok|}} Plan and prototype future release engineering architecture [Get Firefox on a Growth Trajectory / Scale FirefoxOS]

[https://etherpad.mozilla.org/devservices-Q22014 Full list]

=== Security & Privacy ===
Full list here: [[SecurityEngineering/2014/Q2Goals]]

* Web Platform Security
** {{new|plan out replacement for nsIContentPolicy and start executing}} (dri=tanvi, +sicking,ckerschb)
** {{ok|Make new CSP parser on by default in nightly}} (dri=ckerschb, +grobinson,sstamm)
** {{ok|Land WebCrypto}} (dri=rbarnes) {{Bug|865789}}
* Secure Client Platform
** {{new|Get open.h264 plugin sandboxed on windows}} [dri=sstamm, a=tabraldes]
** {{prev|something about sandboxing logging}} [dri=bobowen, a=sstamm,tabraldes]
* Secure Communications
** {{prev|Land key pinning}} [dri=cviecco, a=keeler,mmc]
** {{new|mozilla::pkix on by default, (riding the train to) / (targeting a) release}} [dri=keeler, a=cviecco]
** {{new| BONUS: Deploy UI for cert error reporting}} [dri=kathleen]
* Tracking Protection / Privacy
** {{ok|Get through the [https://github.com/mozilla/lightbeam/issues/milestones next 2 releases] of Lightbeam}} [dri=mmc, a=grobinson]

Platform/2014-Q2-Goals

2014-04-17T14:36:53Z

Arich: /* Release Engineering Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
=== Layout ===

* {{ok|Table Rendering with DisplayLists}}

* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Vertical text: Implement Layout frame migration to logical coordinates https://etherpad.mozilla.org/css-writing-modes
** {{ok|convert cross-layout classes}}

* Text Performance bugs ( https://etherpad.mozilla.org/textperfworkitems )
** {{ok|large text frames / interruptible reflow}}
** {{ok|enumerated font list fixes}}

* Improve Restyling Performance
** {{ok|bug 977991, and maybe bugs 804975/977594}}

* GFx work items
** {{ok|E10S BasicCompositor}}
** {{ok|GFx tiling}}
** {{ok|Accelerated Filters}}
*** spec work
*** shader & support work

* CSS Flexbox
** {{ok|pagination}}
** recently-finalized spec changes (abspos, min-width, flex sizing) (874718, 984711, 985304)

* Animations & Transitions
** {{ok|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{ok|test_animations covering OMTA}}
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{ok|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|Spec an API for querying basic properties of running CSS animations/transitions}}

* Ship and/or unprefix:
** {{ok|position:sticky}}
** {{ok|Font-features that need fallback support (eg. small-caps)}}

* 3D Transforms
** interop bugs and spec improvement (bug 976365)
** implement preserve-3d proposal
** perf work

* Font Inflation and Reflow-on-Zoom
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* CSS Projects with Adobe
** {{ok|CSS Filters}}
** {{ok|CSS Masking}}
** {{ok|CSS Compositing}}

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Fonts
** {{ok|font load events}}

=== Media ===
=== DOM ===
* {{ok|Implement Xrays to 3 out of the following: Functions ({{bug|976148}}), Objects ({{bug|987111}}), Array/Array-like ({{bug|987163}}), and Error ({{bug|987669}})}}
* {{ok|Get rid of the long tail of C++ objects that are still exposed to the web using XPConnect}}
* {{ok|Get LeakSanitizer builds enabled by default ({{bug|988041}})}}
* {{ok|Identify and fix (DOM stuff, at least) hotspots in b2g app startup (smaug)}}
* {{ok|refactor how tokenizer and tree builder use buffers to reduce memory pressure crashes (hsivonen)}}
* {{ok|Land all non-cache bits of Service Workers preffed-off (on is a bonus) on m-c (nsm)}}
* {{ok|Help guide and review requestAutocomplete backend implementation ({{bug|939351}})}} (likely smaug)

=== WebAPI ===
* {{ok|finalize moving main thread IDB to PBackground including blobs}} (bent)
* {{ok|Convert DataStore cursors and DataStore object itself from JS to C++ (baku)}}
* {{ok|Finalize moving quotamanager to PBackground}} (janv)
* {{ok|clarify design and spec issues around Fetch for Service Workers to ensure they're implementable}} (annevk)

=== JS ===
=== Accessibility ===
* {{ok|Sandboxing support: create and update cached structure of the accessible tree in the parent process (tbsaunde)}}
* {{prev|Windows support: Land basic UIA text navigation implementation (surkov)}}
* {{ok|FFOS/GAIA: under construction (eeejay,marcoz,yzen)}}
Note nicks indicate DRI(s) and all work is collaborative.

=== Perf ===

* Improve Firefox responsiveness & startup time:
** Finish session-store work:
*** {{ok|Improve session-store startup time {{bug|987592}} }}
*** {{ok|Store less data in the sessionstore.js file {{bug|943352}} }}
*** {{ok|Break up janky operations into smaller chunks {{bug|984886}} }}
** Start eliminating top main-thread I/O offenders reported to Telemetry {{bug|572459}}:
*** 1. {{ok|User dictionary (persdict.dat) read on the main thread {{bug|880864}} }}
*** 2. TBD
** {{ok|New storage system for prefs {{bug|897049}} }}
** {{ok|The add-on compatibility dialog should not interrupt startup unless strictly necessary {{bug|760356}} }}
** {{ok|Investigate feasibility of starting Flash plugin instances asynchronously}}

* Fill gaps in test coverage (vs press benchmarks) and prevent regressions:
** {{ok|Create a Talos test for "cold" startup time {{bug|936617}} }}
** {{ok|Create a Talos test for time to restore a previous session {{bug|936630}} }}
** {{ok|Integrate our new power-profiling test into the test infrastructure {{bug|962715}} }}
** {{ok|Automatically detect new sources of main-thread I/O in tests {{bug|935482}} }}
** {{ok|Monitor & track regressions in important Talos tests during each release cycle}}

* Partner with other teams on projects with big perf impact
** {{ok|Assist Necko team with measuring performance of new network cache}}
** {{ok|Make it easier to debug performance regressions by (optionally) capturing profiles during Talos tests {{bug|967619}} }}
** {{ok|Expand use of the T100 tablet/laptop as a reference slow device}}
** {{ok|Work with fx-team on ongoing regressions}}
** {{ok|Add performance tests for OMTC/APZC}}

* Study impact of extensions on Firefox performance
** {{ok|Create a Telemetry dashboard to expose add-ons' impact on Firefox startup time}}

* Grow community:
** {{ok|Mentor at least 5 new external contributors}}

=== Networking ===

* {{ok|Mitigate CSRF attacks against internal networks (block rfc 1918 local addresses from non-local addresses) ({{bug|354493}}) (sworkman) }}
* {{ok|HTTP/2: implement draft-11 of HTTP/2 spec and continue participating in spec development. (hurley / mcmanus) }}
* {{ok|Turn on new HTTP cache in nightly (honza / michal) }}
* {{ok| NetworkLinkService should be enabled so Necko can respond to network changes ({{bug|939318}}) (bagder) }}
* {{ok|B2G: Provide way to "set network offline" per app ({{bug|786419}}) (valentin) }}
* {{ok|Gather data and produce a report on performance wins vs resource costs of the seer on several desktop and mobile scenarios. (hurley) }}

=== Mobile ===
=== A*Team ===
full list: [[Auto-tools/Goals/2014Q2]]

* B2G
** {{ok|}} Deliver v2 of the FxOS Certification Suite
** {{ok|}} Build a common harness for Python and NodeJS Marionette tests, and enable them to run on devices and emulators

* Performance
** {{ok|}} Deploy a Talos dashboard that will allow Talos regressions to be more easily "sheriffed"
** {{ok|}} Improve Eideticker's ability to scale
** {{ok|}} Prototype Datazilla alerts for Talos and Eideticker data

* Mobile
** {{ok|}} Move Android 2.3 reftests off of tegras
** {{ok|}} Designate autophone and/or Eideticker as official perf systems for Android 2.3

* Bugzilla
** {{ok|}} Migrate BMO and upstream Bugzilla CI from Tinderbox to travis-ci.
** {{ok|}} Continue and deepen analysis of BMO perf data.
** {{ok|}} Determine list of possible improvements, estimate gains, prioritize, and implement.

* Treeherder
** {{ok|}} Deploy a production version of Treeherder in coordination with Laura's team
** {{ok|}} Define and implement a sheriff transition plan to move from TBPL to Treeherder
** {{ok|}} Have Treeherder report data to OrangeFactor

* Community
** {{ok|}} Refresh our list of "good first bugs" on a monthly basis
** {{ok|}} Review these and make sure they have adequate information for contributors to start with
** {{ok|}} Keep the numbers of open good first bugs steady or increasing

=== Web Engineering ===
* crash-stats
** {{ok|}} Prototype work to support 100% crash processing for support classification and better user retention after a crash [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Implement symbol upload by partners [Scale FirefoxOS]
** {{ok|}} Better search, graphs, and correlation reports to support QA and Crashkill teams [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Infrastructure improvements to support shipping engineer-requested features faster [Get Firefox on a Growth Trajectory / Scale FxOS]

* FHR
** {{ok|}} Research and develop a plan for addressing sideloading [Invest in Sustainability]

* DXR
** {{ok|}} Move to a more scalable data store to enable indexing all trees [Scale FxOS]
** {{ok|}} Implement search result mixing [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Improve documentation and install to lower the bar for contribution [Enable Communities with Impact]

* l10n
** {{ok|}} (stretch) Remove dependency on buildbot [Enable Communities with Impact]

* Plugincheck
** {{ok|}} Ship new version to support Firefox 29+ [Get Firefox on a Growth Trajectory]

* Air Mozilla
** {{ok|}} Open event editing to all signed in users, wiki style [Enable Communities with Impact]
** {{ok|}} Protoype ability to search by transcript [Enable Communities with Impact]

[https://etherpad.mozilla.org/webeng-q22014 Full list]

=== SUMO and Input ===
* SUMO
** {{ok|}} Implement interactive onboarding for new community volunteers [Enable communities with impact]
** {{ok|}} Implement an initial community hub [Enable communities with impact]
** {{ok|}} Prototype BuddyUp app: interactive support for FirefoxOS [Scale FirefoxOS]

* Input
** {{ok|}} Integrate with Gengo translation API to improve localization [Enable communities with impact]
** {{ok|}} (stretch) Implement and roll out new product-centric dashboards [Scale FirefoxOS]

[https://etherpad.mozilla.org/sumodev-2014-goals Full list]

=== Release Engineering ===
* {{ok|}} Plan and implement a sustainable approach to releases on legacy Android platforms [Get Firefox on a Growth Trajectory]
* {{ok|}} Support infrastructure work on closing scl3 datacenter to save cost [Get Firefox on a Growth Trajectory]
* {{ok|}} Implement automation (slave loan tool) to reduce manual work [Get Firefox on a Growth Trajectory]
* {{ok|}} Stand up device builds for b2g reference phones [Scale FirefoxOS]
* {{ok|}} Remove dependencies on and turn off deprecated systems [Get Firefox on a Growth Trajectory]
* {{ok|}} Audit monitoring and instrumentation of release systems with a view to getting better insight, enabling better agility [Scale FirefoxOS]
* {{ok|}} Continue Balrog (new AUS) rollout to beta, and prepare for release/ESR [Get Firefox on a Growth Trajectory]
* {{ok|}} Automate merge day processes [Get Firefox on a Growth Trajectory]
* Continue infrastructure improvement program:
** {{ok|}} Move more work into the cloud to reduce cost and increase agility [Scale FirefoxOS]
** {{ok|}} Improve build and test environment for Windows [Get Firefox on a Growth Trajectory]
** {{ok|}} Get taskcluster ready to replace buildbot in Q3 and Q3 [Scale FirefoxOS]
* Joint goals with A-team:
** {{ok|}} Design an API that will be the single source of truth about release information [Get Firefox on a Growth Trajectory

[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Ajlqy6z1WDBvdGNxaFFpbnQ4UDdySzZVcGU1RkN4b0E&usp=sharing&pli=1#gid=10 Full list]

=== Release Engineering Operations ===

* Datacenter Consolidation/Cost Reduction
** {{ok| Migrate SCL1 infrastructure to SCL3 and close SCL1 datacenter. {{bug|981124}} }}
** {{ok| Decommission deprecated hardware. {{bug|997213}} and {{bug| 961164}} }}

* Build/Test System Performance Enhancements
** {{ok| Create a POC for Windows build systems on seamicro/SSD hardware and replicate to replace most of the existing Windows build infrastructure if successful. {{bug|982261}} }}
** {{ok| Create a POC for OS X build systems using SSD drives and replicate to the rest of the existing OS X build infrastructure if successful. {{bug|992364}} }}
** {{ok| Architect and deploy a 3-node Ceph Prototype instance if tests on the existing POC show significant build speed increases. {{bug|995512}} }}

* Build/Test System Self-Serve Re-architecture
** {{ok| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} }}
** {{ok| Develop a new image creation solution for 2008R2 build machines which can be used to deploy on bare metal. {{bug|798657}} }}

[https://etherpad.mozilla.org/relops-q22014 Full list]

=== Developer Services ===
* {{ok|}} Review and scale out git architecture [Scale FirefoxOS]
* {{ok|}} (with B-team) Improve performance and review tools for Bugzilla [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{ok|}} (with A-team) Deploy better tree visualization tools [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{ok|}} Plan and prototype future release engineering architecture [Get Firefox on a Growth Trajectory / Scale FirefoxOS]

[https://etherpad.mozilla.org/devservices-Q22014 Full list]

=== Security & Privacy ===
Full list here: [[SecurityEngineering/2014/Q2Goals]]

* Web Platform Security
** {{new|plan out replacement for nsIContentPolicy and start executing}} (dri=tanvi, +sicking,ckerschb)
** {{ok|Make new CSP parser on by default in nightly}} (dri=ckerschb, +grobinson,sstamm)
** {{ok|Land WebCrypto}} (dri=rbarnes) {{Bug|865789}}
* Secure Client Platform
** {{new|Get open.h264 plugin sandboxed on windows}} [dri=sstamm, a=tabraldes]
** {{prev|something about sandboxing logging}} [dri=bobowen, a=sstamm,tabraldes]
* Secure Communications
** {{prev|Land key pinning}} [dri=cviecco, a=keeler,mmc]
** {{new|mozilla::pkix on by default, (riding the train to) / (targeting a) release}} [dri=keeler, a=cviecco]
** {{new| BONUS: Deploy UI for cert error reporting}} [dri=kathleen]
* Tracking Protection / Privacy
** {{ok|Get through the [https://github.com/mozilla/lightbeam/issues/milestones next 2 releases] of Lightbeam}} [dri=mmc, a=grobinson]

Platform/2014-Q2-Goals

2014-04-17T14:35:01Z

Arich: /* Release Operations */

=== Platform ===
==== [[Platform/2014-Goals|2014 General Goals]] ====

=== GFX ===
=== Layout ===

* {{ok|Table Rendering with DisplayLists}}

* Layout to Moz2D
** {{ok|Migrate SVG to Moz2D (bug 703159) }}

* Vertical text: Implement Layout frame migration to logical coordinates https://etherpad.mozilla.org/css-writing-modes
** {{ok|convert cross-layout classes}}

* Text Performance bugs ( https://etherpad.mozilla.org/textperfworkitems )
** {{ok|large text frames / interruptible reflow}}
** {{ok|enumerated font list fixes}}

* Improve Restyling Performance
** {{ok|bug 977991, and maybe bugs 804975/977594}}

* GFx work items
** {{ok|E10S BasicCompositor}}
** {{ok|GFx tiling}}
** {{ok|Accelerated Filters}}
*** spec work
*** shader & support work

* CSS Flexbox
** {{ok|pagination}}
** recently-finalized spec changes (abspos, min-width, flex sizing) (874718, 984711, 985304)

* Animations & Transitions
** {{ok|transitions/animations spec editing}}
** {{ok|transitions refactoring to match new spec (960465)}}
** {{ok|frame reconstruction (625289)}}

* OMTA on non-B2G Platforms (980770)
** {{ok|test_animations covering OMTA}}
** {{ok|fix correctness bugs (cascading, etc.)}}
** {{ok|turning on on other OMTC platforms (Mac/Android)}}

* Web animations:
** {{ok|Spec an API for querying basic properties of running CSS animations/transitions}}

* Ship and/or unprefix:
** {{ok|position:sticky}}
** {{ok|Font-features that need fallback support (eg. small-caps)}}

* 3D Transforms
** interop bugs and spec improvement (bug 976365)
** implement preserve-3d proposal
** perf work

* Font Inflation and Reflow-on-Zoom
** both implementation bug fixing and spec work
** -moz-text-size-adjust

* CSS Projects with Adobe
** {{ok|CSS Filters}}
** {{ok|CSS Masking}}
** {{ok|CSS Compositing}}

* ImageLib
** {{ok|RasterImage for multiple images}}

* CSS Fonts
** {{ok|font load events}}

=== Media ===
=== DOM ===
* {{ok|Implement Xrays to 3 out of the following: Functions ({{bug|976148}}), Objects ({{bug|987111}}), Array/Array-like ({{bug|987163}}), and Error ({{bug|987669}})}}
* {{ok|Get rid of the long tail of C++ objects that are still exposed to the web using XPConnect}}
* {{ok|Get LeakSanitizer builds enabled by default ({{bug|988041}})}}
* {{ok|Identify and fix (DOM stuff, at least) hotspots in b2g app startup (smaug)}}
* {{ok|refactor how tokenizer and tree builder use buffers to reduce memory pressure crashes (hsivonen)}}
* {{ok|Land all non-cache bits of Service Workers preffed-off (on is a bonus) on m-c (nsm)}}
* {{ok|Help guide and review requestAutocomplete backend implementation ({{bug|939351}})}} (likely smaug)

=== WebAPI ===
* {{ok|finalize moving main thread IDB to PBackground including blobs}} (bent)
* {{ok|Convert DataStore cursors and DataStore object itself from JS to C++ (baku)}}
* {{ok|Finalize moving quotamanager to PBackground}} (janv)
* {{ok|clarify design and spec issues around Fetch for Service Workers to ensure they're implementable}} (annevk)

=== JS ===
=== Accessibility ===
* {{ok|Sandboxing support: create and update cached structure of the accessible tree in the parent process (tbsaunde)}}
* {{prev|Windows support: Land basic UIA text navigation implementation (surkov)}}
* {{ok|FFOS/GAIA: under construction (eeejay,marcoz,yzen)}}
Note nicks indicate DRI(s) and all work is collaborative.

=== Perf ===

* Improve Firefox responsiveness & startup time:
** Finish session-store work:
*** {{ok|Improve session-store startup time {{bug|987592}} }}
*** {{ok|Store less data in the sessionstore.js file {{bug|943352}} }}
*** {{ok|Break up janky operations into smaller chunks {{bug|984886}} }}
** Start eliminating top main-thread I/O offenders reported to Telemetry {{bug|572459}}:
*** 1. {{ok|User dictionary (persdict.dat) read on the main thread {{bug|880864}} }}
*** 2. TBD
** {{ok|New storage system for prefs {{bug|897049}} }}
** {{ok|The add-on compatibility dialog should not interrupt startup unless strictly necessary {{bug|760356}} }}
** {{ok|Investigate feasibility of starting Flash plugin instances asynchronously}}

* Fill gaps in test coverage (vs press benchmarks) and prevent regressions:
** {{ok|Create a Talos test for "cold" startup time {{bug|936617}} }}
** {{ok|Create a Talos test for time to restore a previous session {{bug|936630}} }}
** {{ok|Integrate our new power-profiling test into the test infrastructure {{bug|962715}} }}
** {{ok|Automatically detect new sources of main-thread I/O in tests {{bug|935482}} }}
** {{ok|Monitor & track regressions in important Talos tests during each release cycle}}

* Partner with other teams on projects with big perf impact
** {{ok|Assist Necko team with measuring performance of new network cache}}
** {{ok|Make it easier to debug performance regressions by (optionally) capturing profiles during Talos tests {{bug|967619}} }}
** {{ok|Expand use of the T100 tablet/laptop as a reference slow device}}
** {{ok|Work with fx-team on ongoing regressions}}
** {{ok|Add performance tests for OMTC/APZC}}

* Study impact of extensions on Firefox performance
** {{ok|Create a Telemetry dashboard to expose add-ons' impact on Firefox startup time}}

* Grow community:
** {{ok|Mentor at least 5 new external contributors}}

=== Networking ===

* {{ok|Mitigate CSRF attacks against internal networks (block rfc 1918 local addresses from non-local addresses) ({{bug|354493}}) (sworkman) }}
* {{ok|HTTP/2: implement draft-11 of HTTP/2 spec and continue participating in spec development. (hurley / mcmanus) }}
* {{ok|Turn on new HTTP cache in nightly (honza / michal) }}
* {{ok| NetworkLinkService should be enabled so Necko can respond to network changes ({{bug|939318}}) (bagder) }}
* {{ok|B2G: Provide way to "set network offline" per app ({{bug|786419}}) (valentin) }}
* {{ok|Gather data and produce a report on performance wins vs resource costs of the seer on several desktop and mobile scenarios. (hurley) }}

=== Mobile ===
=== A*Team ===
full list: [[Auto-tools/Goals/2014Q2]]

* B2G
** {{ok|}} Deliver v2 of the FxOS Certification Suite
** {{ok|}} Build a common harness for Python and NodeJS Marionette tests, and enable them to run on devices and emulators

* Performance
** {{ok|}} Deploy a Talos dashboard that will allow Talos regressions to be more easily "sheriffed"
** {{ok|}} Improve Eideticker's ability to scale
** {{ok|}} Prototype Datazilla alerts for Talos and Eideticker data

* Mobile
** {{ok|}} Move Android 2.3 reftests off of tegras
** {{ok|}} Designate autophone and/or Eideticker as official perf systems for Android 2.3

* Bugzilla
** {{ok|}} Migrate BMO and upstream Bugzilla CI from Tinderbox to travis-ci.
** {{ok|}} Continue and deepen analysis of BMO perf data.
** {{ok|}} Determine list of possible improvements, estimate gains, prioritize, and implement.

* Treeherder
** {{ok|}} Deploy a production version of Treeherder in coordination with Laura's team
** {{ok|}} Define and implement a sheriff transition plan to move from TBPL to Treeherder
** {{ok|}} Have Treeherder report data to OrangeFactor

* Community
** {{ok|}} Refresh our list of "good first bugs" on a monthly basis
** {{ok|}} Review these and make sure they have adequate information for contributors to start with
** {{ok|}} Keep the numbers of open good first bugs steady or increasing

=== Web Engineering ===
* crash-stats
** {{ok|}} Prototype work to support 100% crash processing for support classification and better user retention after a crash [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Implement symbol upload by partners [Scale FirefoxOS]
** {{ok|}} Better search, graphs, and correlation reports to support QA and Crashkill teams [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Infrastructure improvements to support shipping engineer-requested features faster [Get Firefox on a Growth Trajectory / Scale FxOS]

* FHR
** {{ok|}} Research and develop a plan for addressing sideloading [Invest in Sustainability]

* DXR
** {{ok|}} Move to a more scalable data store to enable indexing all trees [Scale FxOS]
** {{ok|}} Implement search result mixing [Get Firefox on a Growth Trajectory / Scale FxOS]
** {{ok|}} Improve documentation and install to lower the bar for contribution [Enable Communities with Impact]

* l10n
** {{ok|}} (stretch) Remove dependency on buildbot [Enable Communities with Impact]

* Plugincheck
** {{ok|}} Ship new version to support Firefox 29+ [Get Firefox on a Growth Trajectory]

* Air Mozilla
** {{ok|}} Open event editing to all signed in users, wiki style [Enable Communities with Impact]
** {{ok|}} Protoype ability to search by transcript [Enable Communities with Impact]

[https://etherpad.mozilla.org/webeng-q22014 Full list]

=== SUMO and Input ===
* SUMO
** {{ok|}} Implement interactive onboarding for new community volunteers [Enable communities with impact]
** {{ok|}} Implement an initial community hub [Enable communities with impact]
** {{ok|}} Prototype BuddyUp app: interactive support for FirefoxOS [Scale FirefoxOS]

* Input
** {{ok|}} Integrate with Gengo translation API to improve localization [Enable communities with impact]
** {{ok|}} (stretch) Implement and roll out new product-centric dashboards [Scale FirefoxOS]

[https://etherpad.mozilla.org/sumodev-2014-goals Full list]

=== Release Engineering ===
* {{ok|}} Plan and implement a sustainable approach to releases on legacy Android platforms [Get Firefox on a Growth Trajectory]
* {{ok|}} Support infrastructure work on closing scl3 datacenter to save cost [Get Firefox on a Growth Trajectory]
* {{ok|}} Implement automation (slave loan tool) to reduce manual work [Get Firefox on a Growth Trajectory]
* {{ok|}} Stand up device builds for b2g reference phones [Scale FirefoxOS]
* {{ok|}} Remove dependencies on and turn off deprecated systems [Get Firefox on a Growth Trajectory]
* {{ok|}} Audit monitoring and instrumentation of release systems with a view to getting better insight, enabling better agility [Scale FirefoxOS]
* {{ok|}} Continue Balrog (new AUS) rollout to beta, and prepare for release/ESR [Get Firefox on a Growth Trajectory]
* {{ok|}} Automate merge day processes [Get Firefox on a Growth Trajectory]
* Continue infrastructure improvement program:
** {{ok|}} Move more work into the cloud to reduce cost and increase agility [Scale FirefoxOS]
** {{ok|}} Improve build and test environment for Windows [Get Firefox on a Growth Trajectory]
** {{ok|}} Get taskcluster ready to replace buildbot in Q3 and Q3 [Scale FirefoxOS]
* Joint goals with A-team:
** {{ok|}} Design an API that will be the single source of truth about release information [Get Firefox on a Growth Trajectory

[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Ajlqy6z1WDBvdGNxaFFpbnQ4UDdySzZVcGU1RkN4b0E&usp=sharing&pli=1#gid=10 Full list]

=== Release Engineering Operations ===

* Datacenter Consolidation/Cost Reduction
** {{ok| Migrate SCL1 infrastructure to SCL3 and close SCL1 datacenter {{bug|981124}} }}
** {{ok| Decommission deprecated hardware {{bug|997213}} and {{bug| 961164}} }}

* Build/Test System Performance Enhancements
** {{ok| Create a POC for Windows build systems on seamicro/SSD hardware and replicate to replace most of the existing Windows build infrastructure if successful. {{bug|982261}} }}
** {{ok| Create a POC for OS X build systems using SSD drives and replicate to the rest of the existing OS X build infrastructure if successful. {{bug|992364}} }}
** {{ok| Architect and deploy a 3-node Ceph Prototype instance if tests on the existing POC show significant build speed increases. {{bug|995512}} }}

* Build/Test System Self-Serve Re-architecture
** {{ok| Design a private cloud deployment architecture for bare metal and produce a POC that supports Ubuntu 12.04 test machines. {{bug|963165}} }}
** {{ok| Develop a new image creation solution for 2008R2 build machines which can be used to deploy on bare metal {{bug|798657}} }}

[https://etherpad.mozilla.org/relops-q22014 Full list]

=== Developer Services ===
* {{ok|}} Review and scale out git architecture [Scale FirefoxOS]
* {{ok|}} (with B-team) Improve performance and review tools for Bugzilla [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{ok|}} (with A-team) Deploy better tree visualization tools [Get Firefox on a Growth Trajectory / Enable communities with impact]
* {{ok|}} Plan and prototype future release engineering architecture [Get Firefox on a Growth Trajectory / Scale FirefoxOS]

[https://etherpad.mozilla.org/devservices-Q22014 Full list]

=== Security & Privacy ===
Full list here: [[SecurityEngineering/2014/Q2Goals]]

* Web Platform Security
** {{new|plan out replacement for nsIContentPolicy and start executing}} (dri=tanvi, +sicking,ckerschb)
** {{ok|Make new CSP parser on by default in nightly}} (dri=ckerschb, +grobinson,sstamm)
** {{ok|Land WebCrypto}} (dri=rbarnes) {{Bug|865789}}
* Secure Client Platform
** {{new|Get open.h264 plugin sandboxed on windows}} [dri=sstamm, a=tabraldes]
** {{prev|something about sandboxing logging}} [dri=bobowen, a=sstamm,tabraldes]
* Secure Communications
** {{prev|Land key pinning}} [dri=cviecco, a=keeler,mmc]
** {{new|mozilla::pkix on by default, (riding the train to) / (targeting a) release}} [dri=keeler, a=cviecco]
** {{new| BONUS: Deploy UI for cert error reporting}} [dri=kathleen]
* Tracking Protection / Privacy
** {{ok|Get through the [https://github.com/mozilla/lightbeam/issues/milestones next 2 releases] of Lightbeam}} [dri=mmc, a=grobinson]

IT/Projects/2013

2014-02-05T14:48:09Z

Arich: Created page with "* Project Dashboard 2013Q4 * Project Dashboard 2013Q3 * [[IT/Projects/Project-Dashboard-2013Q..."

* [[IT/Projects/Project-Dashboard-2013Q4|Project Dashboard 2013Q4]]
* [[IT/Projects/Project-Dashboard-2013Q3|Project Dashboard 2013Q3]]
* [[IT/Projects/Project-Dashboard-2013Q2|Project Dashboard 2013Q2]]
* [[IT/Projects/Project-Dashboard-2013Q1|Project Dashboard 2013Q1]]

IT/Projects

2014-02-05T14:48:02Z

Arich:

* [[IT/Projects/2013|2013 Project Dashboard]]

* [[IT/Projects/Weekly-Project-Status-Reports|Weekly Project Status Reports]]

ReleaseEngineering/Slave Naming

2014-01-14T19:30:37Z

Arich: /* Current naming differences */

= Introduction =
At Release Engineering we do builds and tests of Firefox, Firefox for Android, Firefox OS and Thunderbird. We also do some other tier-2 type of jobs on the same hardware used to ship the mentioned products.
For builds, we build both on real hardware and VMs (in-house & AWS).
For unit and performance tests (aka talos), we build both on real desktop machines, VMs (EC2) and mobile development boards (tegras & pandas).
As we move everything to scl3, we can see the purpose of the machine indicated on the full hostname (try build machines VS release build machines VS test machines VS "Windows" vlan).

== Notes ==
* We only use "try" for ec2 instances since renaming is harder with in-house hosts
* Moving machines from the try vlan to the build vlan will requires hostname changes (after the first 'dot')

= Proposed naming =
== Desktop hostname convention ==
P-O-T-XXXX

1) P = purpose
* "b-" - for build purposes
* "t-" - for test machines
<br />
2) O = OS + instruction size (optional)
* xp32/w732/w864/2008/2012
** we currently use "w64" for "w2008"
* linux32/linux64
** for linux we camouflage the distro
* snow/lion/mtnlion/mavericks

3) T = Type of hardware
<br />
For VMs:
* "ec2" for Amazon
* "vm" if run in-house
** "vmw" for in-house vmware
<br />
For real hardware:
* "hp" for hp machines
* "ix" for ix machines
* "r#" - # depends on the revision of Mac mini that we use
<br />
4) XXXX = number
<br />
Fixed digits allow lexical sorting, but limit to 9999 slaves per type. This is at variance with numbering throughout the rest of Mozilla, where zero-padding is not used.

=== Examples ===
Build machine examples:
* b-linux64-hp-XXXX
** currently, they're named bld-centos6-hp-XXXX
** bug open to change these - https://bugzil.la/847912
* b-linux64-ec2-XXXX
* b-linux64-vm-XXXX
** we still use *some* in-house Linux build VMs for esr17
* b-2012-ec2-XXXX (15 chars)
** this platform is forward thinking if we build on AWS for Windows
* b-2008-ix-XXXX (14 chars)
** currently named w64-ix-slaveXXX - to be renamed on scl3
* b-lion-r#-XXXX
<br />
Test machine examples:
* t-linux32-ec2-XXXX
* t-linux64-ec2-XXXX
* t-linux32-ix-XXXX
* t-linux64-ix-XXXX
* t-snow-r4-XXXX
* t-mountainlion-r5-XXXX
* t-xp32-ix-XXXX
* t-w732-ix-XXXX
* t-w864-ix-XXXX

== Mobile hostname convention ==
T-XXXX

T = type (e.g. panda or tegra)
Examples:
* panda-XXXX
* tegra-XXXX

== Other infra ==
buildbot-masterXX - for buildbot masters
foopyXXX - for foopy machines

= Current naming differences =
NOTE: Differences are bolded to make it easier to read
As of January, 2014 (note that machines have moved to four digits)
{| border="1" cellpadding="2"
! Proposed
! Current
|-
| b-linux64-{hp.ix}-XXXX
|
* b'''ld-centos6'''-hp-XXX
* b'''ld-linux64'''-ix-XXX
|-
| b-linux64-ec2-XXXX
| b'''ld'''-linux64-ec2-XXX
|-
| b-linux64-vmw-XXXX
| bld-centos5-32-vmw-XXX (not supported)
|-
| b-2008-ix-XXXX
| w64-ix-slaveXXX
|-
| b-2012-ec2-XXXX
|
|-
| b-lion-r#-XXXX
| b'''ld'''-lion-r#-XXX
|-
| t-linux32-ec2-XXXX
| t'''st'''-linux32-ec2-XXX
|-
| t-linux64-ec2-XXXX
| t'''st'''-linux64-ec2-XXX
|-
| t-linux32-ix-XXXX
| talos-linux32-ix-XXX
|-
| t-linux64-ix-XXXX
| talos-linux64-ix-XXX
|-
| t-snow-r4-XXXX
| talos-r4-snow-XXX
|-
| t-mtnlion-r5-XXXX
| talos-mtnlion-r5-XXX
|-
| t-xp32-ix-XXXX
| t-xp32-ix-XXX
|-
| t-w732-ix-XXXX
| t-w732-ix-XXX
|-
| t-w864-ix-XXXX
| t-w864-ix-XXX
|}

ReleaseEngineering/Slave Naming

2014-01-14T19:08:40Z

Arich: /* Current naming differences */

= Introduction =
On Release Engineering we do builds and tests of Firefox, Firefox for Android, Firefox OS and Thunderbird. We also do some other tier-2 type of jobs but we use the same hardware used to ship the mentioned products.
For builds, we build both on real hardware and VMs (in-house & AWS).
For unit and performance tests (aka talos), we build both on real desktop machines, VMs (EC2) and mobile development boards (tegras & pandas).
As we move everything to scl3, we can see the purpose of the machine indicated on the full hostname (try build machines VS release build machines VS test machines VS "Windows" vlan).

== Notes ==
* We only use "try" for ec2 instances since renaming is harder with in-house hosts
* Moving machines from the try vlan to the build vlan will require hostname changes (after the first 'dot')

= Proposed naming =
== Desktop hostname convention ==
P-O-T-XXX

1) P = purpose
* "b-" - for build purposes
* "t-" - for test machines
<br />
2) O = OS + instruction size (optional)
* xp32/w732/w864
* w2008/w2012
** we currently use "w64" for "w2008"
* linux32/linux64
** for linux we camouflage the distro
* snow/lion/mtnlion
<br />
3) T = Type of hardware
For VMs:
* "ec2" for Amazon
* "vm" if run in-house
** "vmw" for in-house vmware
<br />
For real hardware:
* "hp" for hp machines
* "ix" for ix machines
* "r#" - # depends on the revision of Mac mini that we use
<br />
4) XXX = number
Fixed digits allow lexical sorting, but limit to 999 slaves per type. This is at variance with numbering throughout the rest of Mozilla, where zero-padding is not used.

== Examples ==
Build machine examples:
* b-linux64-hp-XXX
** currently is named bld-centos6-hp-XXX
** bug open to change these - https://bugzil.la/847912
* b-linux64-ec2-XXX
* b-linux64-vm-XXX
** we still use *some* in-house Linux build VMs for esr17
* b-w2012-ec2-XXX (15 chars)
** this platform is forward thinking if we build on AWS for Windows
* b-w2008-ix-XXX (14 chars)
** currently named w64-ix-slaveXXX
* b-lion-r#-XXX
<br />
Test machine examples:
* t-linux32-ec2-XXX
* t-linux64-ec2-XXX
* t-linux32-ix-XXX
* t-linux64-ix-XXX
* t-snow-r4-XXX
* t-lion-r4-XXX
* t-mountainlion-r5-XXX
* t-xp32-ix-XXX
* t-w732-ix-XXX
* t-w864-ix-XXX

== Mobile hostname convention ==
T-XXXX

T = type (e.g. panda or tegra)
Examples:
* panda-XXXX
* tegra-XXXX

== Other infra ==
buildbot-masterXX - for buildbot masters
foopyXXX - for foopy machines that

= Current naming differences =
NOTE: Differences are bolded to make it easier to read
As of January, 2014 (note that windows builders have moved to four digits)
{| border="1" cellpadding="2"
! Proposed
! Current
|-
| b-linux64-T-XXX
|
* b'''ld-centos6'''-hp-XXX
* b'''ld-linux64'''-ix-XXX
|-
| b-linux64-ec2-XXX
| b'''ld'''-linux64-ec2-XXX
|-
| b-linux64-vm-XXX
| bld-centos5-32-vmw-XXX (not supported)
|-
| b-2008-ix-XXXX
| w64-ix-slaveXXX
|-
| b-2012-ec2-XXXX
|
|-
| b-lion-r#-XXX
| b'''ld'''-lion-r#-XXX
|-
| t-linux32-ec2-XXX
| t'''st'''-linux32-ec2-XXX
|-
| t-linux64-ec2-XXX
| t'''st'''-linux64-ec2-XXX
|-
| t-linux32-ix-XXX
| talos-linux32-ix-XXX
|-
| t-linux64-ix-XXX
| talos-linux64-ix-XXX
|-
| t-snow-r4-XXX
| talos-r4-snow-XXX
|-
| t-lion-r5-XXX
| talos-r4-lion-XXX
|-
| t-mtnlion-r5-XXX
| talos-mtnlion-r5-XXX
|-
| t-xp32-ix-XXX
| same
|-
| t-w732-ix-XXX
| same
|-
| t-w864-ix-XXX
| same
|}

ReleaseEngineering/Slave Naming

2014-01-13T19:43:15Z

Arich: /* Current naming differences */

= Introduction =
On Release Engineering we do builds and tests of Firefox, Firefox for Android, Firefox OS and Thunderbird. We also do some other tier-2 type of jobs but we use the same hardware used to ship the mentioned products.
For builds, we build both on real hardware and VMs (in-house & AWS).
For unit and performance tests (aka talos), we build both on real desktop machines, VMs (EC2) and mobile development boards (tegras & pandas).
As we move everything to scl3, we can see the purpose of the machine indicated on the full hostname (try build machines VS release build machines VS test machines VS "Windows" vlan).

== Notes ==
* We only use "try" for ec2 instances since renaming is harder with in-house hosts
* Moving machines from the try vlan to the build vlan will require hostname changes (after the first 'dot')

= Proposed naming =
== Desktop hostname convention ==
P-O-T-XXX

1) P = purpose
* "b-" - for build purposes
* "t-" - for test machines
<br />
2) O = OS + instruction size (optional)
* xp32/w732/w864
* w08/w12
** we currently use "w64" for "w08"
* linux32/linux64
** for linux we camouflage the distro
* snow/lion/mtnlion
<br />
3) T = Type of hardware
For VMs:
* "ec2" for Amazon
* "vm" if run in-house
** "vmw" for in-house vmware
<br />
For real hardware:
* "hp" for hp machines
* "ix" for ix machines
* "r#" - # depends on the revision of Mac mini that we use
<br />
4) XXX = number
Fixed digits allow lexical sorting, but limit to 999 slaves per type. This is at variance with numbering throughout the rest of Mozilla, where zero-padding is not used.

== Examples ==
Build machine examples:
* b-linux64-hp-XXX
** currently is named bld-centos6-hp-XXX
** bug open to change these - https://bugzil.la/847912
* b-linux64-ec2-XXX
* b-linux64-vm-XXX
** we still use *some* in-house Linux build VMs for esr17
* b-w12-ec2-XXX (15 chars)
** this platform is forward thinking if we build on AWS for Windows
* b-w08-ix-XXX (14 chars)
** currently named w64-ix-slaveXXX
* b-lion-r#-XXX
<br />
Test machine examples:
* t-linux32-ec2-XXX
* t-linux64-ec2-XXX
* t-linux32-ix-XXX
* t-linux64-ix-XXX
* t-snow-r4-XXX
* t-lion-r4-XXX
* t-mountainlion-r5-XXX
* t-xp32-ix-XXX
* t-w732-ix-XXX
* t-w864-ix-XXX

== Mobile hostname convention ==
T-XXXX

T = type (e.g. panda or tegra)
Examples:
* panda-XXXX
* tegra-XXXX

== Other infra ==
buildbot-masterXX - for buildbot masters
foopyXXX - for foopy machines that

= Current naming differences =
NOTE: Differences are bolded to make it easier to read
As of April, 2013
{| border="1" cellpadding="2"
! Proposed
! Current
|-
| b-linux64-T-XXX
|
* b'''ld-centos6'''-hp-XXX
* b'''ld-linux64'''-ix-XXX
|-
| b-linux64-ec2-XXX
| b'''ld'''-linux64-ec2-XXX
|-
| b-linux64-vm-XXX
| bld-centos5-32-vmw-XXX (not supported)
|-
| b-w2008-ix-XXX
| w64-ix-slaveXXX
|-
| b-w2012-ec2-XXX
|
|-
| b-lion-r#-XXX
| b'''ld'''-lion-r#-XXX
|-
| t-linux32-ec2-XXX
| t'''st'''-linux32-ec2-XXX
|-
| t-linux64-ec2-XXX
| t'''st'''-linux64-ec2-XXX
|-
| t-linux32-ix-XXX
| talos-linux32-ix-XXX
|-
| t-linux64-ix-XXX
| talos-linux64-ix-XXX
|-
| t-snow-r4-XXX
| talos-r4-snow-XXX
|-
| t-lion-r5-XXX
| talos-r4-lion-XXX
|-
| t-mtnlion-r5-XXX
| talos-mtnlion-r5-XXX
|-
| t-xp32-ix-XXX
| same
|-
| t-w732-ix-XXX
| same
|-
| t-w864-ix-XXX
| same
|}

Mobile/Testing/09 11 13

2013-09-11T17:08:25Z

Arich:

= Previous Action Items =
* ctalbert to get lg g2x to mtn view to be replaced in eideticker set up
* ctalbert to get sheriffs involved to look into what happened with the fx inbound merge

= Status reports =
== Dev team ==
== Rel Eng ==

* (pmoore) Watcher upgrade scheduled for Friday 13th.
* (kmoir) green mozharness Android talos tests in staging, testing patches to enable jit tests
* (armenzg/Callek) Android x86 tests running on cedar

== IT ==
* Started planning discussions for movement of infrastructure out of SCL1 and into SCL3. SCL1 lease is up on 7/31/2014.
* Working with A-Team, RelEng and WPR to plan the Tegra move from MTV to the new Evelyn office.
* {{bug|856123}} New and improved panda self diagnostic tests are now running in mozpool
* Panda-recovery is now handled by DCOPs directly
* {{bug|914472}} New Android 4.0.4 image w/ latest sutagent (1.19) and watcher (1.16) will be available in mozpool today

== A Team ==
* tegra failure rate: [[http://54.215.155.53/data/android2.2 1.88%]]
* panda failure rate: [[http://54.215.155.53/data/android4.0 20.5%]]
** excluding retries: 1.72

* Mobile Bugs in Orange Factor Top 10
** {{Bug|910106}} Intermittent Android tcheck2 talosError: 'Verify HomePager is hidden: HomePager is hidden [browser_output.txt]'

* Landed mozharness patch for {{Bug|858621}} to run jit-tests
* {{Bug|907351}} Panda reftests now run significantly slower
** '''Still''' bisecting this
* {{Bug|892569}} Run remote cpp unittests
** Mozharness patch should be ready this week

== x86 automation ==
* latest results on Ash are encouraging: M1-M8, X passing; rc1, rc2 almost passing
* investigating robocop crashes, reftest failures

== Autophone ==
* [bc] I haven't yet contacted QA for help with reviewing the results and filing bugs. Will reach out today.

== Eideticker ==
= Round Table =
* {{Bug|910092}} virtualized testing for android

= Action Items =

Mobile/Testing/09 11 13

2013-09-11T16:57:45Z

Arich:

= Previous Action Items =
* ctalbert to get lg g2x to mtn view to be replaced in eideticker set up
* ctalbert to get sheriffs involved to look into what happened with the fx inbound merge

= Status reports =
== Dev team ==
== Rel Eng ==

* (pmoore) Watcher upgrade scheduled for Friday 13th.
* (kmoir) green mozharness Android talos tests in staging, testing patches to enable jit tests
* (armenzg/Callek) Android x86 tests running on cedar

== IT ==
*Started planning discussions for movement of infrastructure out of SCL1 and into SCL3. SCL1 lease is up on 7/31/2014.
*Working with A-Team, RelEng and WPR to plan the Tegra move from MTV to the new Evelyn office.
*New and improved panda self diagnostic tests are now running in mozpool
*Panda-recovery is now handled by DCOPs directly
*New Android 4.0.4 image w/ latest sutagent (1.19) and watcher (1.16) will be available in mozpool today

== A Team ==
* tegra failure rate: [[http://54.215.155.53/data/android2.2 1.88%]]
* panda failure rate: [[http://54.215.155.53/data/android4.0 20.5%]]
** excluding retries: 1.72

* Mobile Bugs in Orange Factor Top 10
** {{Bug|910106}} Intermittent Android tcheck2 talosError: 'Verify HomePager is hidden: HomePager is hidden [browser_output.txt]'

* Landed mozharness patch for {{Bug|858621}} to run jit-tests
* {{Bug|907351}} Panda reftests now run significantly slower
** '''Still''' bisecting this
* {{Bug|892569}} Run remote cpp unittests
** Mozharness patch should be ready this week

== x86 automation ==
* latest results on Ash are encouraging: M1-M8, X passing; rc1, rc2 almost passing
* investigating robocop crashes, reftest failures

== Autophone ==

== Eideticker ==
= Round Table =
* {{Bug|910092}} virtualized testing for android

= Action Items =