MozillaWiki - User contributions [en]

Responsibilities of the Quantum Profiling Pool

2017-12-04T16:21:48Z

Naveed: Created page with "We would like to make the Quantum Profiling Pool a standard process. Dave Camp and engineering leadership believe increasing our capacity for profiling is essential to realizi..."

We would like to make the Quantum Profiling Pool a standard process. Dave Camp and engineering leadership believe increasing our capacity for profiling is essential to realizing our 2018 performance goals. This is where your help comes in. I would like one representative (at minimum) from each key component, as listed in the Sheet, to be on the Quantum Profiling Pool. The responsibilities of this group are as follows.

*
* They will serve for one Quantum Flow iteration (three firefox releases). The next iteration ends Mar 12, 2018 when FF60 leaves Nightly for Beta (https://wiki.mozilla.org/RapidRelease/Calendar ).
* They should be able to commit to at least half-a-day a week to profiling.
* Their work will come out of Quantum Release Criteria, Quantum Flow and other performance bugs that are marked with whiteboard: [qf:needs-analysis]. These will be assigned round-robin if a component is unknown.
* They will profile the bug until
**they are able to assign it to a component
**Suggest next steps to address it based on what they have seen in their analysis
**Suggest a [qf:p1], [qf:p3] , or [qf:p5] priority via comment.
**The whiteboard tag should transition from [qf:needs-analysis] to [qf:analyzed].
*If the Quantum Flow triage team agrees we will update the whiteboard priority. We may move it back to [qf:needs-analysis] if more information is needed to make the bug actionable.
*Members of the Quantum Profiling Pool can and should make use of all available resources to help them analyze a bug such as
**Performance wiki “How to gecko profile” - https://wiki.mozilla.org/Quantum/Release_Criteria#Resources_on_.22How_to_do_Gecko_Profiling.22
**How to use the profiler - https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler
**Gecko Profiler FAQ - https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Gecko_Profiler_FAQ
**IRC #flow to ask for help if/when they get stuck on a particular profile
*Ultimately they are responsible for the [qf:needs-analysis] bugs they have been assigned to. Ensuring that their profile analysis leads to an actionable bug resolution.

Performance bugs often linger in Bugzilla with no activity for lack of profiling. We believe this process will help address that profiling capacity shortfall all performance bugs are experiencing. This process should also have the additional benefit of training our engineers to become more capable at diagnosing and correcting performance bugs over time. Both profiling and performance needs to continue as a discipline.

Quantum/Release Criteria

2017-12-04T16:19:07Z

Naveed: /* Links */

* '''QRC''' = Quantum Release Criteria
* '''QF''' = Quantum Flow

= Bug Workflow =

A '''QRC''' bug is a bug that indicates Firefox is below some performance target on a QRC benchmark or metric.

QRC bug states:
# '''"[QRC][QRC_NeedAnalysis]"''' and '''unassigned''' (ready for profile analysis)
# '''"[QRC][QRC_NeedAnalysis]"''' and '''assigned''' to an engineer analyzing the profile
# '''"[QRC][QRC_Analyzed][qf:p1]"''' and '''unassigned''' (ready to be fixed by a QF engineer)
# '''"[QRC][QRC_Analyzed][qf:p1]"''' and '''assigned''' to a QF engineer fixing the bug

# Testers will:
## File a new bug for any QRC test failures that don't already have a bug.
## Make the new bug block one of the [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1370336&maxdepth=1&hide_resolved=1 QRC meta bugs].
## Attach a link to a [https://perf-html.io/ Gecko Profiler] profile.
## Add the whiteboard tag "[QRC][QRC_NeedAnalysis]".
# Profile analysis engineers on the [https://docs.google.com/spreadsheets/u/1/d/1KsoE7QcGZPCXJ6GfqzDiuX4QrnBOjG42Kd12wFCsV-s/ "Profiler Overflow" list]:
## Select a bug from the "Bugs Ready To Be Analyzed" list below.
## Assign the bug to yourself while you are analyzing it.
## If the bug is invalid or not actionable, then needinfo the reporter or close the bug.
##* There might not be obvious, visible problems. The profile analysis does not necessarily require the profile analysis engineer to reproduce the test case, just identify if there are obvious hot spots in the profile.
## If you can't identify the root cause, then unassign yourself. Another profile analysis engineer will pick it from the QRC_NeedAnalysis list, so leave any notes you have or needinfo someone who may have domain knowledge relevant to the profile.
## If you have identified the root cause, then:
### Change the whiteboard tag from "[QRC_NeedAnalysis]" to "[QRC_Analyzed][qf:p1]" (so the bug will be seen by QF engineers).
### Move the bug to an appropriate Bugzilla component.
### Unassign yourself.

= Resources on "How to do Gecko Profiling"=

If you have questions about using the Gecko Profiler, operators are ready standing by to help in the #flow IRC channel. :)

'''Ehsan's videos on how to analyze Gecko profiles'''
* [https://air.mozilla.org/gecko-profiler-introduction Introduction to Gecko profiler]
* [https://air.mozilla.org/gecko-and-native-profiler Introduction to Gecko and Native profiler]

'''Mike's deep dive videos analyzing profiles on real bugs'''
* [https://air.mozilla.org/search/?q=joy+of+profiling Search for "''Joy of Profiling''" on Air Mozilla. '''Effective Dec 4, 2017 - 15 episodes''']
* [https://air.mozilla.org/the-joy-of-profiling-pilot The Joy of Profiling - Pilot]
* [https://air.mozilla.org/the-joy-of-profiling-pilot-2 The Joy of Profiling - Pilot 2] 
* [https://air.mozilla.org/the-joy-of-profiling-episode-1-20170519 The Joy of Profiling - Episode 1 Posted on May 19/2017] 
* [https://air.mozilla.org/the-joy-of-profiling-episode-2 The Joy of Profiling - Episode 2 Posted on June 10/2017]
* [https://air.mozilla.org/the-joy-of-profiling-episode-3 The Joy of Profiling - Episode 3 Posted on June 17/2017]
* [https://air.mozilla.org/the-joy-of-profiling-episode-4 The Joy of Profiling - Episode 4 Posted on June 24/2017]
* [https://air.mozilla.org/the-joy-of-profiling-episode-5 The Joy of Profiling - Episode 5 Posted on July 8/2017]
* [https://air.mozilla.org/the-joy-of-profiling-episode-6 The Joy of Profiling - Episode 6 Posted on July 15/2017]

= Bugs Ready To Be Analyzed =

QRC_NeedAnalysis bugs:

<bugzilla> {
"status_whiteboard": "[QRC_NeedAnalysis]",
"assigned_to": "nobody@mozilla.org",
"resolution": "---",
"include_fields": "id, priority, summary, whiteboard, assigned_to",
"order": "id"
} </bugzilla>

= Bugs Now Being Analyzed =

QRC_NeedAnalysis bugs:

<bugzilla> {
"f1": "status_whiteboard",
"o1": "substring",
"v1": "[QRC_NeedAnaly",
"f2": "assigned_to",
"o2": "notequals",
"v2": "nobody@mozilla.org",
"resolution": "---",
"include_fields": "id, priority, summary, whiteboard, assigned_to, last_change_time",
"order": "assigned_to"
} </bugzilla>

= Bugs Ready To Be Fixed =

QRC_Analyzed bugs that are ready to be fixed by a QF engineer:

<bugzilla> {
"status_whiteboard": "[QRC_Analyzed],[qf:p1]",
"resolution": "---",
"include_fields": "id, priority, summary, whiteboard, assigned_to",
"order": "id"
} </bugzilla>

QRC_Analyzed bugs that are missing the [qf:p1] whiteboard tag:

<bugzilla> {
"status_whiteboard": "[QRC_Analy",
"f1": "status_whiteboard",
"o1": "notsubstring",
"v1": "[qf:p1]",
"resolution": "---",
"include_fields": "id, priority, summary, whiteboard, assigned_to",
"order": "id"
} </bugzilla>

= Links =

[[Responsibilities of the Quantum Profiling Pool]]

QRC queries:
* [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=%5BQRC_NeedAnalysis%5D All QRC_NeedAnalysis bugs]
* [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=%5BQRC_Analyzed%5D All QRC_Analyzed bugs]
* [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=%5BQRC%5D All QRC bugs]
* [https://bugzilla.mozilla.org/buglist.cgi?short_desc=Quantum%20Release%20Criteria&resolution=---&query_format=advanced&short_desc_type=allwordssubstr QRC meta bugs]
* [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&o1=anywordssubstr&resolution=---&emailtype1=exact&o2=nowordssubstr&query_format=advanced&emailassigned_to1=1&f2=status_whiteboard&longdesc=https%3A%2F%2Fperfht.ml%2F&email1=nobody%40mozilla.org&v1=%5Bqf%3Ainvestigate%2C%5Bqf%3Ap1%5D&v2=%5BQRC_Analy&longdesc_type=allwordssubstr QF bugs that have profiles but are unassigned]

Bug Triage

2017-10-30T15:32:44Z

Naveed: /* Initiative Process */ word cleanup

{{LastUpdated}}

{{warning | '''The bug that will overshadow all the hard work we put into the Firefox 57 release has probably already been filed.''' [[Bugmasters/Marking bugs for the Firefox 57 release|We need to find it and fix it]].}}

=What we do=

Mozilla's bugmaster develops policies and processes for managing bugs, their goal is to "leave no bug behind," and help Mozillians make crisp and actionable decisions on bugs, and enable them to follow-through on their decisions.

=Triage Process=

If you're triaging bugs in a component, [[Bugmasters/Process/Triage|Triage for Component Leads]] is the process we follow.

=Initiative Process=

There are a number of workflows in Bugzilla that are in addition to and often across our Component system. These initiative will modify our [https://docs.google.com/a/mozilla.com/document/d/1kZkXdeyTCUWg9KxM5I9ly_Qdo9KOMhlKuEgLtuv0jq8/edit?usp=sharing_eil&ts=59a08dbc Initiative Template] and the modified document will be linked below. Any special tagging required by these initiates will be registered as [[Bugmasters/Process/Metadata|Metadata]] and also described in the Initiative document.

* [https://docs.google.com/document/d/1L6zpmCfQP81HRPRv4Ma5Cj7fDG4qD9mtLFDgH8FHmJ4/edit#heading=h.5bzuz130e1nn Performance Initiative] - Triage and tracking of bugs we believe are essential to Firefox's responsiveness and throughput. NOTE: Update of the Quantum Flow initiative.

{{:Bugmasters/Projects/Bug Handling/Scorecard}}

{{:Bugmasters/Projects/Bug_Handling/Bug_Husbandry}}

{{:Bugmasters/Projects/Bug Handling/Stale Bugs}}

= Firefox 57 Queries =

First Nightly: 2017-06-12

[https://mzl.la/2zKwJAm P1 bugs which are affecting or fix-optional for Firefox 57]; these bugs should be reviewed to see if they are ''still'' P1s and if they should ''not'' be <tt>wontfix</tt>ed.

[https://mzl.la/2llqWhC Bugs marked as `affected` for Firefox 57 by triage status]; un-triaged bugs should be reviewed as early in the cycle as possible.

Bugs filed later in the cycle should only be considered if they will result in a dot release if they are not addressed.

[https://docs.google.com/spreadsheets/d/1k98lDyxm2g2vYMbvrCSnJ46ZTqE9FvRWLwIF-cGlmt0/edit?pli=1#gid=1956742257 Triage stats for this release]

=Who we are=

* Emma Humphries (:emceeaich), Bugmaster [mailto:ehumphries@mozilla.com ehumphries@mozilla.com]
* [[Bugmasters/Project/Bug_Handling/Triage_Leads|The individual triage leads in each bugzilla component ]]

=Projects=
* [[Bugmasters/Projects/Bug Handling|Bug Handling]]: Making sure no bug is left behind
* [[Bugmasters/Projects/Bugzilla Clean Up|Bugzilla Clean Up]]: End-of-life for [https://bugzilla.mozilla.org Bugzilla] components
* [[Bugmasters/Projects/Folk Knowledge|Bugzilla Folk Knowledge]]: Documenting how each team uses bugzilla metadata
* [[Bugmasters/Projects/Bugzilla Training|Bugzilla Training]]: Equip Mozillans with best practices on bugs
* [[Bugmasters/Projects/Repeat Filers|Repeat Filers]]: Track contributions from new Mozillans, so we can get more people filing bugs earlier in the release cycle

=Code=

* [https://github.com/mozilla/bugzilla-readable-status Bugzilla Readable Statuses] - enhancement to bugzilla.mozilla.com to help make the status of a bug more understandable
* [https://github.com/mozilla/triage-center Triage Center] - tool for finding untriaged bugs, and other bugs that need attention
* [https://github.com/mozilla/triage-report Triage Report] - scoreboard for components with most un-triaged bugs

=Meetings=
The bugmaster office has no scheduled meetings at this time.

=Communication=
Get in touch with us. Don't hesitate to communicate using:

* The IRC channel: [irc://irc.mozilla.org#qa irc.mozilla.org#bugmasters]. Join us on IRC to say hello, introduce yourself, and talk about bugs, bugs, bugs. Questions are welcome!
* Joining the [https://lists.mozilla.org/listinfo/bugmasters bugmaster mailing list] to be informed of all the news and the discussions.

=Useful Links=
* [[Bugmasters/Project/Bug_Handling/Triage_Leads|Triage Leads]] - who is responsible for triaging new bugs in each Firefox component
* [[Bugmasters/Guide|Bugmastering Guide]] - A guide helping on how to contribute to bug management and triage
* [[Bugzilla:MozillaFlagsAndSuch|Whiteboard tags]] - A list of common whiteboard field values and flags used in Bugzilla

=== Bugzilla Process and Rules ===

* [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Bugzilla Etiquette (CoC)]
* [https://bugzilla.mozilla.org/page.cgi?id=restrict_comments_guidelines.html Guidelines for Restricting Comments]
* [[BMO/comment_tagging|Comment tagging]]
* [https://bugzilla.mozilla.org/page.cgi?id=get_permissions.html How to request permissions]
* [https://bugzilla.mozilla.org/page.cgi?id=triage_request.html Requesting triage permissions]

Bug Triage

2017-10-30T15:31:40Z

Naveed: Add Initiative Template link, Performance Initiative document link and internal link to new Metadata (whiteboard tagging) sub page that will be linked by Bugzilla.

{{LastUpdated}}

{{warning | '''The bug that will overshadow all the hard work we put into the Firefox 57 release has probably already been filed.''' [[Bugmasters/Marking bugs for the Firefox 57 release|We need to find it and fix it]].}}

=What we do=

Mozilla's bugmaster develops policies and processes for managing bugs, their goal is to "leave no bug behind," and help Mozillians make crisp and actionable decisions on bugs, and enable them to follow-through on their decisions.

=Triage Process=

If you're triaging bugs in a component, [[Bugmasters/Process/Triage|Triage for Component Leads]] is the process we follow.

=Initiative Process=

There are a number of workflows in Bugzilla that are in addition to and often across our Component system. These initiative will modify our [https://docs.google.com/a/mozilla.com/document/d/1kZkXdeyTCUWg9KxM5I9ly_Qdo9KOMhlKuEgLtuv0jq8/edit?usp=sharing_eil&ts=59a08dbc Initiative Template] and must be document below. Any special tagging required by these initiates will be registered as [[Bugmasters/Process/Metadata|Metadata]] and also described in the Initiative document.

* [https://docs.google.com/document/d/1L6zpmCfQP81HRPRv4Ma5Cj7fDG4qD9mtLFDgH8FHmJ4/edit#heading=h.5bzuz130e1nn Performance Initiative] - Triage and tracking of bugs we believe are essential to Firefox's responsiveness and throughput. NOTE: Update of the Quantum Flow initiative.

{{:Bugmasters/Projects/Bug Handling/Scorecard}}

{{:Bugmasters/Projects/Bug_Handling/Bug_Husbandry}}

{{:Bugmasters/Projects/Bug Handling/Stale Bugs}}

= Firefox 57 Queries =

First Nightly: 2017-06-12

[https://mzl.la/2zKwJAm P1 bugs which are affecting or fix-optional for Firefox 57]; these bugs should be reviewed to see if they are ''still'' P1s and if they should ''not'' be <tt>wontfix</tt>ed.

[https://mzl.la/2llqWhC Bugs marked as `affected` for Firefox 57 by triage status]; un-triaged bugs should be reviewed as early in the cycle as possible.

Bugs filed later in the cycle should only be considered if they will result in a dot release if they are not addressed.

[https://docs.google.com/spreadsheets/d/1k98lDyxm2g2vYMbvrCSnJ46ZTqE9FvRWLwIF-cGlmt0/edit?pli=1#gid=1956742257 Triage stats for this release]

=Who we are=

* Emma Humphries (:emceeaich), Bugmaster [mailto:ehumphries@mozilla.com ehumphries@mozilla.com]
* [[Bugmasters/Project/Bug_Handling/Triage_Leads|The individual triage leads in each bugzilla component ]]

=Projects=
* [[Bugmasters/Projects/Bug Handling|Bug Handling]]: Making sure no bug is left behind
* [[Bugmasters/Projects/Bugzilla Clean Up|Bugzilla Clean Up]]: End-of-life for [https://bugzilla.mozilla.org Bugzilla] components
* [[Bugmasters/Projects/Folk Knowledge|Bugzilla Folk Knowledge]]: Documenting how each team uses bugzilla metadata
* [[Bugmasters/Projects/Bugzilla Training|Bugzilla Training]]: Equip Mozillans with best practices on bugs
* [[Bugmasters/Projects/Repeat Filers|Repeat Filers]]: Track contributions from new Mozillans, so we can get more people filing bugs earlier in the release cycle

=Code=

* [https://github.com/mozilla/bugzilla-readable-status Bugzilla Readable Statuses] - enhancement to bugzilla.mozilla.com to help make the status of a bug more understandable
* [https://github.com/mozilla/triage-center Triage Center] - tool for finding untriaged bugs, and other bugs that need attention
* [https://github.com/mozilla/triage-report Triage Report] - scoreboard for components with most un-triaged bugs

=Meetings=
The bugmaster office has no scheduled meetings at this time.

=Communication=
Get in touch with us. Don't hesitate to communicate using:

* The IRC channel: [irc://irc.mozilla.org#qa irc.mozilla.org#bugmasters]. Join us on IRC to say hello, introduce yourself, and talk about bugs, bugs, bugs. Questions are welcome!
* Joining the [https://lists.mozilla.org/listinfo/bugmasters bugmaster mailing list] to be informed of all the news and the discussions.

=Useful Links=
* [[Bugmasters/Project/Bug_Handling/Triage_Leads|Triage Leads]] - who is responsible for triaging new bugs in each Firefox component
* [[Bugmasters/Guide|Bugmastering Guide]] - A guide helping on how to contribute to bug management and triage
* [[Bugzilla:MozillaFlagsAndSuch|Whiteboard tags]] - A list of common whiteboard field values and flags used in Bugzilla

=== Bugzilla Process and Rules ===

* [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Bugzilla Etiquette (CoC)]
* [https://bugzilla.mozilla.org/page.cgi?id=restrict_comments_guidelines.html Guidelines for Restricting Comments]
* [[BMO/comment_tagging|Comment tagging]]
* [https://bugzilla.mozilla.org/page.cgi?id=get_permissions.html How to request permissions]
* [https://bugzilla.mozilla.org/page.cgi?id=triage_request.html Requesting triage permissions]

WeeklyUpdates/2017-08-28

2017-08-28T16:27:48Z

Naveed: /* Speakers */ minor

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* https://air.mozilla.org/channels/project-meeting/ to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
{{conf|8600}}
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
* Big thanks to the Brazil Community that participated in the last [http://braziljs.org/ BrazilJS] in Porto Alegre. Special thanks to Andre Garzia, Cynthia Pereira, Adriano Cupello, Marina Limeria, Luigui Delyer, Beatriz Rizental, Felipe do Espirito Santo, Dalmo veras Neto, Rodrigo Waters and Rabimba Karanjai (as special guest). Also kudos to Salva de la Puente, Vlad Filipov and Mike Taylor for being amazing speakers

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
* [https://quality.mozilla.org/event/bug-triage-day-170/ Weekly Bug Triage Day]

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===
* Add-ons Community Meeting
** 17:00 UTC | 10:00am Pacific; ACE Vidyo Room

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* [https://quality.mozilla.org/event/bug-verification-day-185/ Weekly Bug Verification Day]

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Sharing
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Asa Dotzler
| Firefox Roadmap
| Weekly Firefox Update
| MTV
| no
| na
| https://wiki.mozilla.org/Firefox/Roadmap/Updates#2017-08-28
|-
| Azita Rashed
| Director of Engineering, Research
| Emerging Technologies Update
| MTV
| no
| n/a
| https://wiki.mozilla.org/WeeklyUpdates/EmergingTechnology#August_28th.2C_2017
|-
| Naveed Ihsanullah
| Update for FF57 Soft Freeze
| Quantum Flow
| Vidyo
| no
| n/a

| https://docs.google.com/presentation/d/1U4FGZn4q_KN_dmE6DGsdxuilT7iJXR3-AdrAtUIIKJE/edit?usp=sharing
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

{| class="fullwidth-table wikitable"
|-
! ''Who is being introduced?''
! ''Who are you? (the introducer)''
! ''Where are you doing the introduction?''
! ''Where are they from?''
! ''How will they be part of Mozilla?''
|-

|-
| Michael DeAngelo
| David Slater
| San Francisco
| San Francisco
| Chief People Officer
|-
|}

= Fireside Chat =
A chance to hear from leadership at Mozilla, and have a short Q&A about a specific topic.

===This Week===

'''Name''', "Title"

===Topics===

You can submit questions in advance on the Moderator page (link), or ask them live on Air Mozilla using a Mozilla Space mic or in #airmozilla on IRC.

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

WeeklyUpdates/2017-08-28

2017-08-28T16:26:36Z

Naveed: /* Speakers */ naveed added

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* https://air.mozilla.org/channels/project-meeting/ to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
{{conf|8600}}
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
* Big thanks to the Brazil Community that participated in the last [http://braziljs.org/ BrazilJS] in Porto Alegre. Special thanks to Andre Garzia, Cynthia Pereira, Adriano Cupello, Marina Limeria, Luigui Delyer, Beatriz Rizental, Felipe do Espirito Santo, Dalmo veras Neto, Rodrigo Waters and Rabimba Karanjai (as special guest). Also kudos to Salva de la Puente, Vlad Filipov and Mike Taylor for being amazing speakers

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
* [https://quality.mozilla.org/event/bug-triage-day-170/ Weekly Bug Triage Day]

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===
* Add-ons Community Meeting
** 17:00 UTC | 10:00am Pacific; ACE Vidyo Room

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* [https://quality.mozilla.org/event/bug-verification-day-185/ Weekly Bug Verification Day]

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Sharing
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Asa Dotzler
| Firefox Roadmap
| Weekly Firefox Update
| MTV
| no
| na
| https://wiki.mozilla.org/Firefox/Roadmap/Updates#2017-08-28
|-
| Azita Rashed
| Director of Engineering, Research
| Emerging Technologies Update
| MTV
| no
| n/a
| https://wiki.mozilla.org/WeeklyUpdates/EmergingTechnology#August_28th.2C_2017
|-
| Naveed Ihsanullah
| FF57 Soft Freeze
| Quantum Flow Update
| Vidyo
| no
| n/a

| https://docs.google.com/presentation/d/1U4FGZn4q_KN_dmE6DGsdxuilT7iJXR3-AdrAtUIIKJE/edit?usp=sharing
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

{| class="fullwidth-table wikitable"
|-
! ''Who is being introduced?''
! ''Who are you? (the introducer)''
! ''Where are you doing the introduction?''
! ''Where are they from?''
! ''How will they be part of Mozilla?''
|-

|-
| Michael DeAngelo
| David Slater
| San Francisco
| San Francisco
| Chief People Officer
|-
|}

= Fireside Chat =
A chance to hear from leadership at Mozilla, and have a short Q&A about a specific topic.

===This Week===

'''Name''', "Title"

===Topics===

You can submit questions in advance on the Moderator page (link), or ask them live on Air Mozilla using a Mozilla Space mic or in #airmozilla on IRC.

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

WeeklyUpdates/2015-09-14

2015-09-11T19:03:29Z

Naveed: /* Introducing New Hires */ Jakob Olesen

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* http://air.mozilla.org/ to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
* Thanks to Michael Kohler and André Fiedler for coordinating our participation at the upcoming TV Hack Day Berlin!
* Thanks to Anubhav.worklinux for fixing {{bug|1004036}}, making the little things in Firefox OS not just functional, but beautiful.
* Thanks to Durwasa Chakraborty for fixing {{bug|1166202}}, making the Firefox OS RTL support more complete.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===
'''Thursday September 24, 2015, 9am PT / noon ET / 4pm UTC - Mozilla Mountain View + [https://air.mozilla.org/september-brantina/ Air Mozilla]'''
''''Monthly Brantina: "[https://air.mozilla.org/september-brantina/ Should I Put it On Yammer?]"''''
How do you respond when people at Mozilla ask you this? Do you sigh, roll your eyes, let out a small resigned laugh? Most of us know that many seemingly-benign posts can devolve into a debate nobody expected, necessarily wanted or knows what to do with. Our September Brantina speaker, [http://deannazandt.com Deanna Zandt] will provide a deeper understanding of how our brains work when we’re engaged in online discussions which can help us communicate better, make better decisions, be more productive, and ultimately engage with more people driving richer, more dynamic outcomes.
''Our monthly [[Speaker_Series|Speaker Series]] aka Brantinas are for the public so please invite your colleagues to attend live or via the stream. Views represented by our speakers do not necessarily reflect the views of Mozilla.''

== Project Status Updates (voice updates) ==

=== Firefox and Cloud Services ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:''

=== CTO Update ===
''Speaker Location:''

=== Content Services ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Sharing
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME New Volunteer]
! [https://mozillians.org/u/USERNAME Introduced by]
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be contributing from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-
| Sam Giles
| Wilson Page
| London Office
| London Office
| FirefoxOS (inc. B2GDroid)
|-
| Jakob Olesen
| Jim Blandy
| Portland Office
| Portland Office
| JavaScript JIT/ARM to begin
|-
|}

== Introducing New Interns ==
{| class="fullwidth-table wikitable"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== Web QA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

Platform/60fps

2015-07-02T19:46:57Z

Naveed: /* Borrowed from Content Performance Program */

== Overall Goal ==

Enable a smooth and responsive user experience for Firefox desktop and mobile users.

== Justification ==

=== Competitive versus other browsers ===
We believe or have data that hangs, jank, and other forms of poor performance result in users moving to other browsers. [evidence needed]

=== Competitive versus native ===
"Both aspects here are important. Making existing content less janky
makes it easier to compete against other browsers. Making it easier to
create jank-free content makes it easier for the web to compete
against native." - jonas

== Implementation Strategy ==

=== Outstanding Issues ===
* How do we work with [[Firefox/Content_Performance_Program | Firefox Content Performance program]]
* What forms of jank are we prioritizing?
* What are our use cases, projects, sites that we prioritize
* How do we measure? How do we automate that measure and see our progress over time?

=== How do we measure ===
* Specific use cases with Top-N sites and measure frame rate
* Video (compositing on-time).
* Animations (compositing on-time, JavaScript/main thread latency+throughput)
* WebGL/WebVR (compositing on-time, input latency, main thread latency, and JavaScript throughput).
* Scrolling (compositing on-time, input latency, and layout/painting).

=== Sites we care about ===
Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE.

==== Borrowed from [https://wiki.mozilla.org/Firefox/Content_Performance_Program Content Performance Program] ====
* [https://www.facebook.com/barackobama www.facebook.com] - President Obama's public profile
* [http://www.twitter.com www.twitter.com]
* [https://search.yahoo.com/yhs/search?p=60+fps&ei=UTF-8&hspart=mozilla&hsimp=yhs-004 Yahoo Search Results]

==== Extended ====
* [http://www.nytimes.com www.nytimes.com]
* [http://www.latimes.com www.latimes.com]
* [http://www.foxnews.com www.foxnews.com]
* [http://www.engadget.com www.engadget.com]
* [http://www.tumblr.com www.tumblr.com]
* [http://www.macrumors.com www.macrumors.com]

=== Internal Projects we care about ===
* Gaia Team
* FFOS Team
* Partner Engineering
* Games
* WebVR
* Shumway

=== External Projects ===
And a list of 5 web frameworks that are likely focal points for concerns along these lines.

===Identify existing programs that have the same or similar goals ===
When will they land? If they land did they solve the problem?

*[[Firefox/Content_Performance_Program | Firefox Content Performance program]]
*Async pan zoom
*Off main thread compositing
*Project Silk
*E10S

== Logistics ==

=== People ===
*Product sponsor/driver: naveed
*Engineering program manager:
*Platform Teams and Team champions:
JavaScript/naveed,
*Technical lead(s):

=== Communication and Discussions ===
* Etherpad: [https://etherpad.mozilla.org/platform-60fps-2015 platform-60fps-2015]

Platform/60fps

2015-07-02T19:46:28Z

Naveed: /* Borrowed from Content Performance Program */

== Overall Goal ==

Enable a smooth and responsive user experience for Firefox desktop and mobile users.

== Justification ==

=== Competitive versus other browsers ===
We believe or have data that hangs, jank, and other forms of poor performance result in users moving to other browsers. [evidence needed]

=== Competitive versus native ===
"Both aspects here are important. Making existing content less janky
makes it easier to compete against other browsers. Making it easier to
create jank-free content makes it easier for the web to compete
against native." - jonas

== Implementation Strategy ==

=== Outstanding Issues ===
* How do we work with [[Firefox/Content_Performance_Program | Firefox Content Performance program]]
* What forms of jank are we prioritizing?
* What are our use cases, projects, sites that we prioritize
* How do we measure? How do we automate that measure and see our progress over time?

=== How do we measure ===
* Specific use cases with Top-N sites and measure frame rate
* Video (compositing on-time).
* Animations (compositing on-time, JavaScript/main thread latency+throughput)
* WebGL/WebVR (compositing on-time, input latency, main thread latency, and JavaScript throughput).
* Scrolling (compositing on-time, input latency, and layout/painting).

=== Sites we care about ===
Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE.

==== Borrowed from [https://wiki.mozilla.org/Firefox/Content_Performance_Program Content Performance Program] ====
* [https://www.facebook.com/barackobama www.facebook.com President Obama's public profile]
* [http://www.twitter.com www.twitter.com]
* [https://search.yahoo.com/yhs/search?p=60+fps&ei=UTF-8&hspart=mozilla&hsimp=yhs-004 Yahoo Search Results]

==== Extended ====
* [http://www.nytimes.com www.nytimes.com]
* [http://www.latimes.com www.latimes.com]
* [http://www.foxnews.com www.foxnews.com]
* [http://www.engadget.com www.engadget.com]
* [http://www.tumblr.com www.tumblr.com]
* [http://www.macrumors.com www.macrumors.com]

=== Internal Projects we care about ===
* Gaia Team
* FFOS Team
* Partner Engineering
* Games
* WebVR
* Shumway

=== External Projects ===
And a list of 5 web frameworks that are likely focal points for concerns along these lines.

===Identify existing programs that have the same or similar goals ===
When will they land? If they land did they solve the problem?

*[[Firefox/Content_Performance_Program | Firefox Content Performance program]]
*Async pan zoom
*Off main thread compositing
*Project Silk
*E10S

== Logistics ==

=== People ===
*Product sponsor/driver: naveed
*Engineering program manager:
*Platform Teams and Team champions:
JavaScript/naveed,
*Technical lead(s):

=== Communication and Discussions ===
* Etherpad: [https://etherpad.mozilla.org/platform-60fps-2015 platform-60fps-2015]

Platform/60fps

2015-07-02T19:44:57Z

Naveed: /* Sites we care about */ split top three to synch with FF content performance program

== Overall Goal ==

Enable a smooth and responsive user experience for Firefox desktop and mobile users.

== Justification ==

=== Competitive versus other browsers ===
We believe or have data that hangs, jank, and other forms of poor performance result in users moving to other browsers. [evidence needed]

=== Competitive versus native ===
"Both aspects here are important. Making existing content less janky
makes it easier to compete against other browsers. Making it easier to
create jank-free content makes it easier for the web to compete
against native." - jonas

== Implementation Strategy ==

=== Outstanding Issues ===
* How do we work with [[Firefox/Content_Performance_Program | Firefox Content Performance program]]
* What forms of jank are we prioritizing?
* What are our use cases, projects, sites that we prioritize
* How do we measure? How do we automate that measure and see our progress over time?

=== How do we measure ===
* Specific use cases with Top-N sites and measure frame rate
* Video (compositing on-time).
* Animations (compositing on-time, JavaScript/main thread latency+throughput)
* WebGL/WebVR (compositing on-time, input latency, main thread latency, and JavaScript throughput).
* Scrolling (compositing on-time, input latency, and layout/painting).

=== Sites we care about ===
Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE.

==== Borrowed from [https://wiki.mozilla.org/Firefox/Content_Performance_Program Content Performance Program] ====
* [http://www.facebook.com www.facebook.com]
* [http://www.twitter.com www.twitter.com]
* [https://search.yahoo.com/yhs/search?p=60+fps&ei=UTF-8&hspart=mozilla&hsimp=yhs-004 Yahoo Search Results]

==== Extended ====
* [http://www.nytimes.com www.nytimes.com]
* [http://www.latimes.com www.latimes.com]
* [http://www.foxnews.com www.foxnews.com]
* [http://www.engadget.com www.engadget.com]
* [http://www.tumblr.com www.tumblr.com]
* [http://www.macrumors.com www.macrumors.com]

=== Internal Projects we care about ===
* Gaia Team
* FFOS Team
* Partner Engineering
* Games
* WebVR
* Shumway

=== External Projects ===
And a list of 5 web frameworks that are likely focal points for concerns along these lines.

===Identify existing programs that have the same or similar goals ===
When will they land? If they land did they solve the problem?

*[[Firefox/Content_Performance_Program | Firefox Content Performance program]]
*Async pan zoom
*Off main thread compositing
*Project Silk
*E10S

== Logistics ==

=== People ===
*Product sponsor/driver: naveed
*Engineering program manager:
*Platform Teams and Team champions:
JavaScript/naveed,
*Technical lead(s):

=== Communication and Discussions ===
* Etherpad: [https://etherpad.mozilla.org/platform-60fps-2015 platform-60fps-2015]

Platform/60fps

2015-06-26T23:44:28Z

Naveed: /* Internal Projects we care about */ added more teams and clarified WebVR is different and possibly different priority than Games

== Overall Goal ==

Enable a smooth and responsive user experience for Firefox desktop and mobile users.

== Justification ==

=== Competitive versus other browsers ===
We believe or have data that hangs, jank, and other forms of poor performance result in users moving to other browsers. [evidence needed]

=== Competitive versus native ===
"Both aspects here are important. Making existing content less janky
makes it easier to compete against other browsers. Making it easier to
create jank-free content makes it easier for the web to compete
against native." - jonas

== Implementation Strategy ==

=== Outstanding Issues ===
* How do we work with [[Firefox/Content_Performance_Program | Firefox Content Performance program]]
* What forms of jank are we prioritizing?
* What are our use cases, projects, sites that we prioritize
* How do we measure? How do we automate that measure and see our progress over time?

=== How do we measure ===
* Specific use cases with Top-N sites and measure frame rate
* Video (compositing on-time).
* Animations (compositing on-time, JavaScript/main thread latency+throughput)
* WebGL/WebVR (compositing on-time, input latency, main thread latency, and JavaScript throughput).
* Scrolling (compositing on-time, input latency, and layout/painting).

=== Sites we care about ===
Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE. Perhaps measu
* [http://www.facebook.com www.facebook.com]
* [http://www.twitter.com www.twitter.com]
* [http://www.nytimes.com www.nytimes.com]
* [http://www.latimes.com www.latimes.com]
* [http://www.foxnews.com www.foxnews.com]
* [http://www.engadget.com www.engadget.com]
* [http://www.tumblr.com www.tumblr.com]
* [http://www.macrumors.com www.macrumors.com]

=== Internal Projects we care about ===
* Gaia Team
* FFOS Team
* Partner Engineering
* Games
* WebVR
* Shumway

=== External Projects ===
And a list of 5 web frameworks that are likely focal points for concerns along these lines.

===Identify existing programs that have the same or similar goals ===
When will they land? If they land did they solve the problem?

*[[Firefox/Content_Performance_Program | Firefox Content Performance program]]
*Async pan zoom
*Off main thread compositing
*Project Silk
*E10S

== Logistics ==

=== People ===
*Product sponsor/driver: naveed
*Engineering program manager:
*Platform Teams and Team champions:
JavaScript/naveed,
*Technical lead(s):

=== Communication and Discussions ===
* Etherpad: [https://etherpad.mozilla.org/platform-60fps-2015 platform-60fps-2015]

Platform/60fps

2015-06-26T21:28:08Z

Naveed: /* People */ add etherpad

== Overall Goal ==

Enable a smooth and responsive user experience for Firefox desktop and mobile users.

== Justification ==

=== Competitive versus other browsers ===
We believe or have data that hangs, jank, and other forms of poor performance result in users moving to other browsers. [evidence needed]

=== Competitive versus native ===
"Both aspects here are important. Making existing content less janky
makes it easier to compete against other browsers. Making it easier to
create jank-free content makes it easier for the web to compete
against native." - jonas

== Implementation Strategy ==

=== Outstanding Issues ===
* How do we work with [[Firefox/Content_Performance_Program | Firefox Content Performance program]]
* What forms of jank are we prioritizing?
* What are our use cases, projects, sites that we prioritize
* How do we measure? How do we automate that measure and see our progress over time?

=== How do we measure ===
* Specific use cases with Top-N sites and measure frame rate
* Video (compositing on-time).
* Animations (compositing on-time, JavaScript/main thread latency+throughput)
* WebGL/WebVR (compositing on-time, input latency, main thread latency, and JavaScript throughput).
* Scrolling (compositing on-time, input latency, and layout/painting).

=== Sites we care about ===
Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE. Perhaps measu
* [http://www.facebook.com www.facebook.com]
* [http://www.twitter.com www.twitter.com]
* [http://www.nytimes.com www.nytimes.com]
* [http://www.latimes.com www.latimes.com]
* [http://www.foxnews.com www.foxnews.com]
* [http://www.engadget.com www.engadget.com]
* [http://www.tumblr.com www.tumblr.com]
* [http://www.macrumors.com www.macrumors.com]

=== Internal Projects we care about ===
* Gaia Team
* Partner Engieneering
* Games/VR
* Shumway

=== External Projects ===
And a list of 5 web frameworks that are likely focal points for concerns along these lines.

===Identify existing programs that have the same or similar goals ===
When will they land? If they land did they solve the problem?

*[[Firefox/Content_Performance_Program | Firefox Content Performance program]]
*Async pan zoom
*Off main thread compositing
*Project Silk
*E10S

== Logistics ==

=== People ===
*Product sponsor/driver: naveed
*Engineering program manager:
*Platform Teams and Team champions:
JavaScript/naveed,
*Technical lead(s):

=== Communication and Discussions ===
* Etherpad: [https://etherpad.mozilla.org/platform-60fps-2015 platform-60fps-2015]

Platform/60fps

2015-06-26T21:17:37Z

Naveed: /* How do we measure */

== Overall Goal ==

Enable a smooth and responsive user experience for Firefox desktop and mobile users.

== Justification ==

=== Competitive versus other browsers ===
We believe or have data that hangs, jank, and other forms of poor performance result in users moving to other browsers. [evidence needed]

=== Competitive versus native ===
"Both aspects here are important. Making existing content less janky
makes it easier to compete against other browsers. Making it easier to
create jank-free content makes it easier for the web to compete
against native." - jonas

== Implementation Strategy ==

=== Outstanding Issues ===
* How do we work with [[Firefox/Content_Performance_Program | Firefox Content Performance program]]
* What forms of jank are we prioritizing?
* What are our use cases, projects, sites that we prioritize
* How do we measure? How do we automate that measure and see our progress over time?

=== How do we measure ===
* Specific use cases with Top-N sites and measure frame rate
* Video (compositing on-time).
* Animations (compositing on-time, JavaScript/main thread latency+throughput)
* WebGL/WebVR (compositing on-time, input latency, main thread latency, and JavaScript throughput).
* Scrolling (compositing on-time, input latency, and layout/painting).

=== Sites we care about ===
Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE. Perhaps measu
* [http://www.facebook.com www.facebook.com]
* [http://www.twitter.com www.twitter.com]
* [http://www.nytimes.com www.nytimes.com]
* [http://www.latimes.com www.latimes.com]
* [http://www.foxnews.com ww.foxnews.com]
* [http://www.engadget.com www.engadget.com]
* [http://www.tumblr.com www.tumblr.com]
* [http://www.macrumors.com www.macrumors.com]

=== Internal Projects we care about ===
* Gaia Team
* Partner Engieneering
* Games/VR
* Shumway

=== External Projects ===
And a list of 5 web frameworks that are likely focal points for concerns along these lines.

===Identify existing programs that have the same or similar goals ===
When will they land? If they land did they solve the problem?

*[[Firefox/Content_Performance_Program | Firefox Content Performance program]]
*Async pan zoom
*Off main thread compositing
*Project Silk
*E10S

== People ==
*Product sponsor/driver: naveed
*Engineering program manager:
*Platform Teams and Team champions:
JavaScript/naveed,
*Technical lead(s):

Platform/60fps

2015-06-26T21:16:16Z

Naveed: /* Justification */

== Overall Goal ==

Enable a smooth and responsive user experience for Firefox desktop and mobile users.

== Justification ==

=== Competitive versus other browsers ===
We believe or have data that hangs, jank, and other forms of poor performance result in users moving to other browsers. [evidence needed]

=== Competitive versus native ===
"Both aspects here are important. Making existing content less janky
makes it easier to compete against other browsers. Making it easier to
create jank-free content makes it easier for the web to compete
against native." - jonas

== Implementation Strategy ==

=== Outstanding Issues ===
* How do we work with [[Firefox/Content_Performance_Program | Firefox Content Performance program]]
* What forms of jank are we prioritizing?
* What are our use cases, projects, sites that we prioritize
* How do we measure? How do we automate that measure and see our progress over time?

=== How do we measure ===
* Video (compositing on-time).
* Animations (compositing on-time, JavaScript/main thread latency+throughput)
* WebGL/WebVR (compositing on-time, input latency, main thread latency, and JavaScript throughput).
* Scrolling (compositing on-time, input latency, and layout/painting).

=== Sites we care about ===
Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE. Perhaps measu
* [http://www.facebook.com www.facebook.com]
* [http://www.twitter.com www.twitter.com]
* [http://www.nytimes.com www.nytimes.com]
* [http://www.latimes.com www.latimes.com]
* [http://www.foxnews.com ww.foxnews.com]
* [http://www.engadget.com www.engadget.com]
* [http://www.tumblr.com www.tumblr.com]
* [http://www.macrumors.com www.macrumors.com]

=== Internal Projects we care about ===
* Gaia Team
* Partner Engieneering
* Games/VR
* Shumway

=== External Projects ===
And a list of 5 web frameworks that are likely focal points for concerns along these lines.

===Identify existing programs that have the same or similar goals ===
When will they land? If they land did they solve the problem?

*[[Firefox/Content_Performance_Program | Firefox Content Performance program]]
*Async pan zoom
*Off main thread compositing
*Project Silk
*E10S

== People ==
*Product sponsor/driver: naveed
*Engineering program manager:
*Platform Teams and Team champions:
JavaScript/naveed,
*Technical lead(s):

Platform/60fps

2015-06-26T21:15:16Z

Naveed: /* Implementation Strategy */

== Overall Goal ==

Enable a smooth and responsive user experience for Firefox desktop and mobile users.

== Justification ==

We believe or have data that hangs, jank, and other forms of poor performance result in users moving to other browsers. [evidence needed]

"Both aspects here are important. Making existing content less janky
makes it easier to compete against other browsers. Making it easier to
create jank-free content makes it easier for the web to compete
against native." - jonas

== Implementation Strategy ==

=== Outstanding Issues ===
* How do we work with [[Firefox/Content_Performance_Program | Firefox Content Performance program]]
* What forms of jank are we prioritizing?
* What are our use cases, projects, sites that we prioritize
* How do we measure? How do we automate that measure and see our progress over time?

=== How do we measure ===
* Video (compositing on-time).
* Animations (compositing on-time, JavaScript/main thread latency+throughput)
* WebGL/WebVR (compositing on-time, input latency, main thread latency, and JavaScript throughput).
* Scrolling (compositing on-time, input latency, and layout/painting).

=== Sites we care about ===
Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE. Perhaps measu
* [http://www.facebook.com www.facebook.com]
* [http://www.twitter.com www.twitter.com]
* [http://www.nytimes.com www.nytimes.com]
* [http://www.latimes.com www.latimes.com]
* [http://www.foxnews.com ww.foxnews.com]
* [http://www.engadget.com www.engadget.com]
* [http://www.tumblr.com www.tumblr.com]
* [http://www.macrumors.com www.macrumors.com]

=== Internal Projects we care about ===
* Gaia Team
* Partner Engieneering
* Games/VR
* Shumway

=== External Projects ===
And a list of 5 web frameworks that are likely focal points for concerns along these lines.

===Identify existing programs that have the same or similar goals ===
When will they land? If they land did they solve the problem?

*[[Firefox/Content_Performance_Program | Firefox Content Performance program]]
*Async pan zoom
*Off main thread compositing
*Project Silk
*E10S

== People ==
*Product sponsor/driver: naveed
*Engineering program manager:
*Platform Teams and Team champions:
JavaScript/naveed,
*Technical lead(s):

Platform/60fps

2015-06-26T21:13:53Z

Naveed: /* Justification */

== Overall Goal ==

Enable a smooth and responsive user experience for Firefox desktop and mobile users.

== Justification ==

We believe or have data that hangs, jank, and other forms of poor performance result in users moving to other browsers. [evidence needed]

"Both aspects here are important. Making existing content less janky
makes it easier to compete against other browsers. Making it easier to
create jank-free content makes it easier for the web to compete
against native." - jonas

=== Implementation Strategy ===

==== Outstanding Issues ====
* How do we work with [[Firefox/Content_Performance_Program | Firefox Content Performance program]]
* What forms of jank are we prioritizing?
* What are our use cases, projects, sites that we prioritize
* How do we measure? How do we automate that measure and see our progress over time?

==== How do we measure ====
* Video (compositing on-time).
* Animations (compositing on-time, JavaScript/main thread latency+throughput)
* WebGL/WebVR (compositing on-time, input latency, main thread latency, and JavaScript throughput).
* Scrolling (compositing on-time, input latency, and layout/painting).

==== Sites we care about ====
Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE. Perhaps measu
* [http://www.facebook.com www.facebook.com]
* [http://www.twitter.com www.twitter.com]
* [http://www.nytimes.com www.nytimes.com]
* [http://www.latimes.com www.latimes.com]
* [http://www.foxnews.com ww.foxnews.com]
* [http://www.engadget.com www.engadget.com]
* [http://www.tumblr.com www.tumblr.com]
* [http://www.macrumors.com www.macrumors.com]

==== Internal Projects we care about ====
* Gaia Team
* Partner Engieneering
* Games/VR
* Shumway

==== External Projects ====
And a list of 5 web frameworks that are likely focal points for concerns along these lines.

====Identify existing programs that have the same or similar goals ====
When will they land? If they land did they solve the problem?

*[[Firefox/Content_Performance_Program | Firefox Content Performance program]]
*Async pan zoom
*Off main thread compositing
*Project Silk
*E10S

== People ==
*Product sponsor/driver: naveed
*Engineering program manager:
*Platform Teams and Team champions:
JavaScript/naveed,
*Technical lead(s):

Platform/60fps

2015-06-26T20:57:20Z

Naveed: Created page with "== Overall Goal == Enable a smooth and responsive user experience for Firefox desktop and mobile users. == Justification == We believe or have data the hangs, jank, and oth..."

== Overall Goal ==

Enable a smooth and responsive user experience for Firefox desktop and mobile users.

== Justification ==

We believe or have data the hangs, jank, and other forms of poor performance result in users moving to other browsers. [evidence needed]

"Both aspects here are important. Making existing content less janky
makes it easier to compete against other browsers. Making it easier to
create jank-free content makes it easier for the web to compete
against native." - jonas

=== Implementation Strategy ===

==== Outstanding Issues ====
* How do we work with [[Firefox/Content_Performance_Program | Firefox Content Performance program]]
* What forms of jank are we prioritizing?
* What are our use cases, projects, sites that we prioritize
* How do we measure? How do we automate that measure and see our progress over time?

==== How do we measure ====
* Video (compositing on-time).
* Animations (compositing on-time, JavaScript/main thread latency+throughput)
* WebGL/WebVR (compositing on-time, input latency, main thread latency, and JavaScript throughput).
* Scrolling (compositing on-time, input latency, and layout/painting).

==== Sites we care about ====
Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE. Perhaps measu
* [http://www.facebook.com www.facebook.com]
* [http://www.twitter.com www.twitter.com]
* [http://www.nytimes.com www.nytimes.com]
* [http://www.latimes.com www.latimes.com]
* [http://www.foxnews.com ww.foxnews.com]
* [http://www.engadget.com www.engadget.com]
* [http://www.tumblr.com www.tumblr.com]
* [http://www.macrumors.com www.macrumors.com]

==== Internal Projects we care about ====
* Gaia Team
* Partner Engieneering
* Games/VR
* Shumway

==== External Projects ====
And a list of 5 web frameworks that are likely focal points for concerns along these lines.

====Identify existing programs that have the same or similar goals ====
When will they land? If they land did they solve the problem?

*[[Firefox/Content_Performance_Program | Firefox Content Performance program]]
*Async pan zoom
*Off main thread compositing
*Project Silk
*E10S

== People ==
*Product sponsor/driver: naveed
*Engineering program manager:
*Platform Teams and Team champions:
JavaScript/naveed,
*Technical lead(s):

Platform

2015-06-26T20:33:35Z

Naveed: /* Mozilla Platform Functional Groups */ add projects and initiatives section

This wiki page is devoted to the planning, scheduling, and documenting of meetings, discussions, and status of the Mozilla platform teams.

== Planning ==
* See [[Platform/Planning | The Platform Planning Page]] for notes on upcoming releases and planning events. (NOTE: this used to be the [[Platform/Post1.9Planning | Post1.9Planning Spreadsheets for all releases after 1.9.]]).
* See also [[Firefox/Namoroka#Firefox.next Platform Requirements]] and its talk page.
* See also the [[Platform/Wanted|Wanted]] page for a few items wanted by extension/application developers

== Platform Team Goals ==
{| class="wikitable" style="text-align: center; width: 500px"
|-
! scope="row" | 2015
| [[Platform/2015-Q1-Goals | Q1 Goals]] || [[Platform/2015-Q2-Goals | Q2 Goals]] || [[Platform/2015-Q3-Goals | Q3 Goals]] || [[Platform/2015-Q4-Goals | Q4 Goals]]
|-
! scope="row" | 2014
| [[Platform/2014-Q1-Goals | Q1 Goals]] || [[Platform/2014-Q2-Goals | Q2 Goals]] || [[Platform/2014-Q3-Goals | Q3 Goals]] || [[Platform/2014-Q4-Goals | Q4 Goals]]
|-
! scope="row" | 2013
| [[Platform/2013-Q1-Goals | Q1 Goals]] || [[Platform/2013-Q2-Goals | Q2 Goals]] || [[Platform/2013-Q3-Goals | Q3 Goals]] || [[Platform/2013-Q4-Goals | Q4 Goals]]
|-
! scope="row" | 2012
| [[Platform/2012-Q1-Goals | Q1 Goals]] || [[Platform/2012-Q2-Goals | Q2 Goals]] || [[Platform/2012-Q3-Goals | Q3 Goals]] || [[Platform/2012-Q4-Goals | Q4 Goals]]
|-
! scope="row" | 2011
| [[Platform/2011-Q1-Goals | Q1 Goals]] || [[Platform/2011-Q2-Goals | Q2 Goals]] || [[Platform/2011-Q3-Goals | Q3 Goals]] || [[Platform/2011-Q4-Goals | Q4 Goals]]
|-
! scope="row" | 2010
| [[Platform/2010-Q1-Goals | Q1 Goals]] || [[Platform/2010-Q2-Goals | Q2 Goals]] || [[Platform/2010-Q3-Goals | Q3 Goals]] || [[Platform/2010-Q4-Goals | Q4 Goals]]
|-
! scope="row" | 2009
| [[Platform/2009-Q1-Goals | Q1 Goals]] || [[Platform/2009-Q2-Goals | Q2 Goals]] || [[Platform/2009-Q3-Goals | Q3 Goals]] || [[Platform/2009-Q4-Goals | Q4 Goals]]
|-
! scope="row" | 2008
| [[Platform/2008-Q1-Goals | Q1 Goals]] || [[Platform/2008-Q2-Goals | Q2 Goals]] || [[Platform/2008-Q3-Goals | Q3 Goals]] || [[Platform/2008-Q4-Goals | Q4 Goals]]
|-
! scope="row" | 2007
| - || [[Platform/2007-Q2-Goals | Q2 Goals]] || [[Platform/2007-Q3-Goals | Q3 Goals]] || [[Platform/2007-Q4-Goals | Q4 Goals]]
|}

== Meeting Notes ==



Create a new weekly agenda from the [[Platform/0-0-0|template]]:
<createbox>
align=left
type=create
preload=Platform/0-0-0
default={{#time: Y-m-d | tuesday}}
prefix=Platform/
</createbox>

==== 2015 ====
{| class="toccolours" style="width: 100%"
|{{Special:PrefixIndex/Platform/2015}}
|}

==== 2014 ====
{| class="toccolours" style="width: 100%"
|{{Special:PrefixIndex/Platform/2014}}
|}

==== 2013 ====
{| class="toccolours" style="width: 100%"
|{{Special:PrefixIndex/Platform/2013}}
|}

==== 2012 ====
{| class="toccolours" style="width: 100%"
|{{Special:PrefixIndex/Platform/2012}}
|}

==== 2011 ====
{| class="toccolours" style="width: 100%"
|{{Special:PrefixIndex/Platform/2011}}
|}

==== 2010 ====
{| class="toccolours" style="width: 100%"
|{{Special:PrefixIndex/Platform/2010}}
|}

==== 2009 ====
{| class="toccolours" style="width: 100%"
|{{Special:PrefixIndex/Platform/2009}}
|}

==== 2008 ====
{| class="toccolours" style="width: 100%"
|{{Special:PrefixIndex/Platform/1.9.1}}
|}

{| class="toccolours" style="width: 100%"
|{{Special:PrefixIndex/Platform/2008}}
|}

==== 2007 ====
{| class="toccolours" style="width: 100%"
|{{Special:PrefixIndex/Platform/2007}}
|}

=== Mozilla Platform Functional Groups ===
Some teams have their own meetings during the week to discuss specific issues:
* [[Platform/Layout | Layout Team]]
* [[Platform/GFX | Graphics Team]]
* [[Platform/Mac | Mac Team]]
* [[Platform/DOM | DOM Team]]
* [[JavaScript:Home_Page | JavaScript Team]]

==Platform Active Projects==
Current major feature or initiatives in Platform
* [[Platform/60fps | 60 FPS Initiative]]

== All Platform pages ==
Visit [[Special:PrefixIndex/{{FULLPAGENAME}}/]] to see all subpages of "{{FULLPAGENAME}}" on {{SERVERNAME}}.

Platform/2015-02-03

2015-02-03T19:13:04Z

Naveed: /* JS (naveed) */ changes

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
* Calendar links: [https://www.google.com/calendar/ical/mozilla.com_p51ksu9ddgqt72f0jl21vaq76o%40group.calendar.google.com/public/basic.ics iCal ics] or [https://www.google.com/calendar/feeds/mozilla.com_p51ksu9ddgqt72f0jl21vaq76o%40group.calendar.google.com/public/basic Atom/XML feed]
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* Join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
{{conf|98411}}
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}
* Firefox 36 Beta 6
** Desktop shipped today
** Mobile should ship shortly (today as well)

* Next Beta builds
** Desktop Beta 7 gtb Thursday
*** Reviewing MSE status for 36 before gtb
** Mobile Beta 8 gtb Monday

* Beta 36 stability is not in good shape - stability rate 2.8 and should be in the range 1.0-1.2
** Looks like primarily gfx bugs, may be related to MSE
* Aurora 37 stability is still not in good shape - stability index is 4.9 and should be < 2.0
** {{Bug|1120331}} (IPC, GFX-related) - 25-30% of crashes
** {{Bug|1123544}} (gfx::GetCairoSurfaceForSourceSurface) 3.2% of crashes

* Update for OpenH264 1.3 is currently being tested on Beta, should move to release soon

===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)
* hg -> git [https://groups.google.com/forum/#!topic/mozilla.dev.platform/Fjarci8tilw replication of gecko] is fixed now. post-mortem happening later this week.

===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===








===CritSmash (dbolter)===








===MemShrink (njn)===


{{readonly}}
No update.




===Stability (kairo)===








* [http://arewestableyet.com/ Overall crash rates] still look bad everywhere else than desktop release.
** Esp. on Beta 36, but also Aurora 37, GFX and media/MSE crashes seem to be the highest issues, often coupled with low memory, also recently introduced shutdownhang crashes are quite high.
** Flash crashes and hangs are sharply down, probably due to sandbox changes along with some effect from MSE.
** Refer to today's [[Firefox/Channels/Meetings/2015-02-03|channel meeting notes]] (once they are up on the wiki) for specific bug numbers.

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===








===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Services (gps/lthomson)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===







* [https://fetch.spec.whatwg.org/ Fetch] [https://bugzilla.mozilla.org/show_bug.cgi?id=1039846 landed] recently (still behind pref)
* parts of Service Worker are landing
* Custom Elements (Web Components) still being figured out (https://wiki.whatwg.org/wiki/CustomElements has info and pointers)

===Electrolysis (e10s) (blassey)===


{{readonly}}





* Please help test e10s in Nightly!
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect
* We've reduced content-process crashes by 40%
** See {{bug|1127374}} and {{bug|1127379}}.
** More fixes to come!

===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===








===GFX (milan)===

* Issues in Beta 36. WebGL, OOM, driver resets, unsupported combinations.

===JS (naveed)===


{{readonly}}

* Compiler (JIT)
** {{bug|1118344}}: (Inline SIMD.int32x4.add), {{bug|1112156}}(Unbox SIMD), {{bug|1112162}} (Align Rectifier frames)

* Other
** Asm.js/ARM64 now at 104 passing tests, 10 failing tests

===Layout (jet/dbaron)===


{{readonly}}
* ImageLib regressions in FF 36 causing churn (eg. {{bug|1128188}})
** Landing bug 1128225 should help get us more reliable tests to avoid this in the future.
* IntegerRange template API coming soon ({{bug|1126552}} and others)
* RTL regressions getting fixed on trunk ({{bug|1121748}}.) Already backed out of B2G2.2 and Aurora.
* W3C CSS & SVG working groups meet next week in Sydney. Contact jet, dbaron, or heycam with spec issues to resolve.
* WebKit-compatibility Fennec builds will be available for testing this week (dholbert.)

===Media (mreavy)===


{{readonly}}

1. What has your team done since last week that might impact others?
* Landed WebRTC multistream & MSID support (a big change)
* Landed webrtc_40 update (same codebase from upstream used by Chrome 40)
* Landed PeerConnection test refactor/cleanup (reduce oranges!)
* gcp has working video (getUserMidia) sandboxing code (patch on a bug)
* OpenH264 plugin 1.3 being tested on Beta, Aurora, Nightly (but not on local dev builds)

2. What will your team do this week that might impact others?
* Looking to land renegotiation RSN (going up for review ASAP)
* OpenH264 1.3 should go to release (independent update channel from Firefox)

3. Is anything slowing your team down or getting in their way?
* Lack of time-dilation to put more hours in a day

===Necko (dougt/jduell)===








===Performance (vladan)===








===Seceng (dougt)===








===Shumway (tschneidereit)===






* Planning to enable Shumway whitelisted for IMDb and a couple other video sites.



==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

==Links==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2015-02-03

2015-02-03T19:11:06Z

Naveed: /* JS (naveed) */ tuesday

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
* Calendar links: [https://www.google.com/calendar/ical/mozilla.com_p51ksu9ddgqt72f0jl21vaq76o%40group.calendar.google.com/public/basic.ics iCal ics] or [https://www.google.com/calendar/feeds/mozilla.com_p51ksu9ddgqt72f0jl21vaq76o%40group.calendar.google.com/public/basic Atom/XML feed]
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* Join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
{{conf|98411}}
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}
* Firefox 36 Beta 6
** Desktop shipped today
** Mobile should ship shortly (today as well)

* Next Beta builds
** Desktop Beta 7 gtb Thursday
*** Reviewing MSE status for 36 before gtb
** Mobile Beta 8 gtb Monday

* Beta 36 stability is not in good shape - stability rate 2.8 and should be in the range 1.0-1.2
** Looks like primarily gfx bugs, may be related to MSE
* Aurora 37 stability is still not in good shape - stability index is 4.9 and should be < 2.0
** {{Bug|1120331}} (IPC, GFX-related) - 25-30% of crashes
** {{Bug|1123544}} (gfx::GetCairoSurfaceForSourceSurface) 3.2% of crashes

* Update for OpenH264 1.3 is currently being tested on Beta, should move to release soon

===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)
* hg -> git [https://groups.google.com/forum/#!topic/mozilla.dev.platform/Fjarci8tilw replication of gecko] is fixed now. post-mortem happening later this week.

===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===








===CritSmash (dbolter)===








===MemShrink (njn)===


{{readonly}}
No update.




===Stability (kairo)===








* [http://arewestableyet.com/ Overall crash rates] still look bad everywhere else than desktop release.
** Esp. on Beta 36, but also Aurora 37, GFX and media/MSE crashes seem to be the highest issues, often coupled with low memory, also recently introduced shutdownhang crashes are quite high.
** Flash crashes and hangs are sharply down, probably due to sandbox changes along with some effect from MSE.
** Refer to today's [[Firefox/Channels/Meetings/2015-02-03|channel meeting notes]] (once they are up on the wiki) for specific bug numbers.

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===








===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Services (gps/lthomson)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===







* [https://fetch.spec.whatwg.org/ Fetch] [https://bugzilla.mozilla.org/show_bug.cgi?id=1039846 landed] recently (still behind pref)
* parts of Service Worker are landing
* Custom Elements (Web Components) still being figured out (https://wiki.whatwg.org/wiki/CustomElements has info and pointers)

===Electrolysis (e10s) (blassey)===


{{readonly}}





* Please help test e10s in Nightly!
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect
* We've reduced content-process crashes by 40%
** See {{bug|1127374}} and {{bug|1127379}}.
** More fixes to come!

===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===








===GFX (milan)===

* Issues in Beta 36. WebGL, OOM, driver resets, unsupported combinations.

===JS (naveed)===


{{readonly}}

* Compiler (JIT)
** {{bug|1118344}}: (Inline SIMD.int32x4.add), {{bug|1112156}}(Unbox SIMD), {{bug|1112162}} (Align Rectifier frames)

===Layout (jet/dbaron)===


{{readonly}}
* ImageLib regressions in FF 36 causing churn (eg. {{bug|1128188}})
** Landing bug 1128225 should help get us more reliable tests to avoid this in the future.
* IntegerRange template API coming soon ({{bug|1126552}} and others)
* RTL regressions getting fixed on trunk ({{bug|1121748}}.) Already backed out of B2G2.2 and Aurora.
* W3C CSS & SVG working groups meet next week in Sydney. Contact jet, dbaron, or heycam with spec issues to resolve.
* WebKit-compatibility Fennec builds will be available for testing this week (dholbert.)

===Media (mreavy)===


{{readonly}}

1. What has your team done since last week that might impact others?
* Landed WebRTC multistream & MSID support (a big change)
* Landed webrtc_40 update (same codebase from upstream used by Chrome 40)
* Landed PeerConnection test refactor/cleanup (reduce oranges!)
* gcp has working video (getUserMidia) sandboxing code (patch on a bug)
* OpenH264 plugin 1.3 being tested on Beta, Aurora, Nightly (but not on local dev builds)

2. What will your team do this week that might impact others?
* Looking to land renegotiation RSN (going up for review ASAP)
* OpenH264 1.3 should go to release (independent update channel from Firefox)

3. Is anything slowing your team down or getting in their way?
* Lack of time-dilation to put more hours in a day

===Necko (dougt/jduell)===








===Performance (vladan)===








===Seceng (dougt)===








===Shumway (tschneidereit)===






* Planning to enable Shumway whitelisted for IMDb and a couple other video sites.



==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

==Links==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2015-01-27

2015-01-27T19:05:46Z

Naveed: /* JS (naveed) */ clear

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
* Calendar links: [https://www.google.com/calendar/ical/mozilla.com_p51ksu9ddgqt72f0jl21vaq76o%40group.calendar.google.com/public/basic.ics iCal ics] or [https://www.google.com/calendar/feeds/mozilla.com_p51ksu9ddgqt72f0jl21vaq76o%40group.calendar.google.com/public/basic Atom/XML feed]
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* Join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
{{conf|98411}}
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lsblakk/sylvestre/lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}
* We shipped [https://www.mozilla.org/en-US/firefox/35.0.1/releasenotes/ Firefox Desktop 35.0.1] last week with a number of bug fixes

* Beta 4
** Desktop ships today
** Mobile ships tomorrow

* Next Beta release
** Desktop Beta 5 gtb Thu, ships Fri
** Mobile Beta 6 gtb Mon, ships Tue/Wed

* Significant stability issues currently on Beta and Aurora/Dev Edition. Bugs are active but may benefit from new eyes.
** Beta
*** {{Bug|1124880}}, {{bug|1116812}}, {{bug|1089454}}, {{bug|1124249}}
** Aurora
*** {{Bug|1120331}} is 25% of all crashes

===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===








===CritSmash (dbolter)===








===MemShrink (njn)===





* Seth Fowler has [https://bugzilla.mozilla.org/show_bug.cgi?id=1122704#c7 resolved] a series of image-related memory usage regressions that have been present on [https://areweslimyet.com AWSY] since early November.




===Stability (kairo)===


{{readonly}}
* [http://arewestableyet.com/ Overall numbers] are still bad for everything other than desktop release (see beta/devedition bugs above, nightly crash rates are even worse).

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===








===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Services (gps/lthomson)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===








===Electrolysis (e10s) (blassey)===








* Please help test e10s in Nightly!
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect

===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===








===GFX (milan)===

* WebGL regression sadness on Windows related to ANGLE. Both in 32/33 (hardware/driver specific) and 35 (investigating.) Bugs 1122465 and 1123365.
* Need to put tooling in place to see if it's shared memory that is soft-leaking, accounting for OOM on Windows.
* Unified crashes due to driver resets, seeing crashreports at #4 which was before a long tail. Should help with tracking down the solutions.

===JS (naveed)===


{{readonly}}

* Compiler (JIT)
** {{bug|1124002}}: Fix a bad performance issue with closure-compiled code (by removing some code).
** {{bug|1125505}}: Posted patches to fix mutable __proto__ to not reshape the proto chain in common cases. This should make Shumway (raytrace.swf) a lot faster.

* Front End and Other
** {{bug|826741}}: Backtracking allocator performance work
** Year In Review: SM in 2014 part 1: http://h4writer.com/?p=14

===Layout (jet/dbaron)===



* Current status of Web Animations API in Firefox: https://birtles.github.io/areweanimatedyet/
* CSS Ruby bug 1039006) will pref on once we have spec clarity (and fixe) for bug 1055662
* Win64 warnings-as-errors (bug 1126017) are turning on once bug 1124029 is in the tree
* Performance profiling on Talos runs (bug 1121571)
* Work in progress on high-priority memory regression (bug 1122704)
* Backed out RTL regression (bug 1121748) for B2G 2.2 but fixing it on trunk in bug 1079154

===Media (mreavy)===


{{readonly}}

1. What has your team done since last week that might impact others?

* {{bug|749703}} from an external contributor broke WebRTC calls by exposing an existing bug/timing-hole (merged to m-c Saturday); a fix is about to land ({{bug|1126036}})
** Some end-to-end functional tests for Hello that are about to land would catch this; most in-single-browser tests as we have in mochitest suites can't/don't hit the timing issue introduced.

2. What will your team do this week that might impact others?
* Landing of webrtc test infrastructure {{bug|1119593}}
* Landing of webrtc Multistream support {{bug|1095218}}
* Landing of WebRTC.org update {{Bug|1109248}}



===Necko (dougt/jduell)===








===Performance (vladan)===




No update this week





===Seceng (dougt)===








===Shumway (tschneidereit)===








===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

==Links==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)
* [http://venturebeat.com/2015/01/21/chrome-40-launches-with-npapi-plugins-blocked-by-default-removes-ssl-3-0-completely/ Chrome 40 launches with NPAPI plugins blocked by default, removes SSL 3.0 completely]. Chrome's Flash plugin is unaffected because it uses PPAPI, not NPAPI.

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2015-01-27

2015-01-27T19:01:08Z

Naveed: /* JS (naveed) */ update

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
* Calendar links: [https://www.google.com/calendar/ical/mozilla.com_p51ksu9ddgqt72f0jl21vaq76o%40group.calendar.google.com/public/basic.ics iCal ics] or [https://www.google.com/calendar/feeds/mozilla.com_p51ksu9ddgqt72f0jl21vaq76o%40group.calendar.google.com/public/basic Atom/XML feed]
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* Join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
{{conf|98411}}
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lsblakk/sylvestre/lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}
* We shipped [https://www.mozilla.org/en-US/firefox/35.0.1/releasenotes/ Firefox Desktop 35.0.1] last week with a number of bug fixes

* Beta 4
** Desktop ships today
** Mobile ships tomorrow

* Next Beta release
** Desktop Beta 5 gtb Thu, ships Fri
** Mobile Beta 6 gtb Mon, ships Tue/Wed

* Significant stability issues currently on Beta and Aurora/Dev Edition. Bugs are active but may benefit from new eyes.
** Beta
*** {{Bug|1124880}}, {{bug|1116812}}, {{bug|1089454}}, {{bug|1124249}}
** Aurora
*** {{Bug|1120331}} is 25% of all crashes

===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===








===CritSmash (dbolter)===








===MemShrink (njn)===





* Seth Fowler has [https://bugzilla.mozilla.org/show_bug.cgi?id=1122704#c7 resolved] a series of image-related memory usage regressions that have been present on [https://areweslimyet.com AWSY] since early November.




===Stability (kairo)===


{{readonly}}
* [http://arewestableyet.com/ Overall numbers] are still bad for everything other than desktop release.

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===








===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Services (gps/lthomson)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===








===Electrolysis (e10s) (blassey)===








* Please help test e10s in Nightly!
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect

===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===








===GFX (milan)===

* WebGL regression sadness on Windows related to ANGLE. Both in 32/33 (hardware/driver specific) and 35 (investigating.) Bugs 1122465 and 1123365.
* Need to put tooling in place to see if it's shared memory that is soft-leaking, accounting for OOM on Windows.
* Unified crashes due to driver resets, seeing crashreports at #4 which was before a long tail. Should help with tracking down the solutions.

===JS (naveed)===


{{readonly}}

* Compiler (JIT)
** {{bug|1124002}}: Fix a bad performance issue with closure-compiled code (by removing some code), bug 1124002.
** {{bug|1125505}}: Posted patches to fix mutable __proto__ to not reshape the proto chain in common cases, bug 1125505. This should make Shumway (raytrace.swf) a lot faster.

* Front End and Other
** {{bug|826741}}: Backtracking allocator performance work
** Year In Review: SM in 2014 part 1: http://h4writer.com/?p=14

===Layout (jet/dbaron)===



* Current status of Web Animations API in Firefox: https://birtles.github.io/areweanimatedyet/
* CSS Ruby bug 1039006) will pref on once we have spec clarity (and fixe) for bug 1055662
* Win64 warnings-as-errors (bug 1126017) are turning on once bug 1124029 is in the tree
* Performance profiling on Talos runs (bug 1121571)
* Work in progress on high-priority memory regression (bug 1122704)
* Backed out RTL regression (bug 1121748) for B2G 2.2 but fixing it on trunk in bug 1079154

===Media (mreavy)===


{{readonly}}

1. What has your team done since last week that might impact others?

* {{bug|749703}} from an external contributor broke WebRTC calls by exposing an existing bug/timing-hole (merged to m-c Saturday); a fix is about to land ({{bug|1126036}})
** Some end-to-end functional tests for Hello that are about to land would catch this; most in-single-browser tests as we have in mochitest suites can't/don't hit the timing issue introduced.

2. What will your team do this week that might impact others?
* Landing of webrtc test infrastructure {{bug|1119593}}
* Landing of webrtc Multistream support {{bug|1095218}}
* Landing of WebRTC.org update {{Bug|1109248}}



===Necko (dougt/jduell)===








===Performance (vladan)===




No update this week





===Seceng (dougt)===








===Shumway (tschneidereit)===








===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

==Links==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)
* [http://venturebeat.com/2015/01/21/chrome-40-launches-with-npapi-plugins-blocked-by-default-removes-ssl-3-0-completely/ Chrome 40 launches with NPAPI plugins blocked by default, removes SSL 3.0 completely]. Chrome's Flash plugin is unaffected because it uses PPAPI, not NPAPI.

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2015-01-20

2015-01-20T19:03:34Z

Naveed: /* JS (naveed) */

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
* Calendar links: [https://www.google.com/calendar/ical/mozilla.com_p51ksu9ddgqt72f0jl21vaq76o%40group.calendar.google.com/public/basic.ics iCal ics] or [https://www.google.com/calendar/feeds/mozilla.com_p51ksu9ddgqt72f0jl21vaq76o%40group.calendar.google.com/public/basic Atom/XML feed]
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* Join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
{{conf|98411}}
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}
* Firefox 35.0.1 candidates:
** {{bug|1117873}} - Firefox crash with "Enhanced Steam" extension since Fx35b1
** {{bug|1113121}} - Godaddy webmail crash [EXCEPTION_ACCESS_VIOLATION_READ]
** {{bug|1121857}} - document.baseURI does not get updated to document.location after base tag is removed from DOM for site with a CSP
** {{bug|1122445}} - CSP change in behavior regards case sensitivity loading resources

* Firefox 36 beta2 gtb Tue, ships Wed (day late due to MLK day in the US)

* Firefox 37 Aurora/Dev Edition updates have been re-enabled

* Firefox 35 post-mortem was held today. Feedback welcome at https://etherpad.mozilla.org/35-0-Post-Mortem

* lsblakk and lmandel both off the rest of this week. Sylvestre is handling all things relman.

===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)
* Tree Closing Window (TCW) Saturday, January 24. Est 0700PT-1500 "Soft Close" (devs must follow up on their own jobs, intermittent outages possible.) Final details TBD. {{bug|1123733|Tracking bug}}.

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===








===CritSmash (dbolter)===








===MemShrink (njn)===







No update.

===Stability (kairo)===








* [http://arewestableyet.com/ Crash rates] currently do not look good anywhere else than desktop release. If you have any topcrash or tracked bugs filed against your team, please help getting them fixed.

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===








===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Services (gps/lthomson)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===








===Electrolysis (e10s) (blassey)===








* Please help test e10s in Nightly!
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect

===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===








===GFX (milan)===

* No update

===JS (naveed)===
{{readonly}}

* Compiler (JIT)
** {{bug|1057082}}: Landed new profiler backend

* Garbage Collection
** {{bug|650161}}: Compacting GC
*** Fixed an issue with uncollected shapes that are never touched except by compacting GC
*** Fixed several test failures and build errors
*** Attempted to land and got backed out

* Front End and Other
** {{bug|1119292}}, {{bug|1119694}}, {{bug|1120207}}, {{bug|1121363}}: PJS removal

===Layout (jet/dbaron)===








===Media (mreavy)===


{{readonly}}

1. What has your team done since last week that might impact others?

* Landed (thanks to Andreas Pehrson) bug 879717 (MediaStream->video_element->canvas works again)

2. What will your team do this week that might impact others?
* Multistream support in WebRTC will reland once one problem is resolved
* Once Multistream lands and sticks, Webrtc upstream update to branch 40 will land
* Hello throttling (limits users who have the Hello button in the toolbar by default, as opposed to in Customize palette) will likely be turned to 100% within the next 1-2 weeks (everyone sees Hello in the toolbar)
* Major rewrite of WebRTC mochitests (bug 1119593)



===Necko (dougt/jduell)===








===Performance (vladan)===




1. What has your team done since last week that might impact others?

* {{bug|1120126}}: Profiling Win64 nightlies should be possible
* Reminder: 3 business days to respond to Talos regressions, 2 weeks to make decision on the regression



3. Is anything slowing your team down or getting in their way?

* If you get frequent or reproducible out-of-memory crashes (especially when Firefox is not actually out of physical memory), please ping me or David Major
* Help us test bug 998863: Asynchronous initialization of plugins
** It's currently preffed '''*OFF*''' by default, please help us test it: set dom.ipc.plugins.asyncInit to true
*** e10s crash issues have been fixed
** Mark any bug reports as blockers of bug 1116806

===Seceng (dougt)===








===Shumway (tschneidereit)===








===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

==Links==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2014-12-16

2014-12-16T19:15:26Z

Naveed: /* JS (naveed) */

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lsblakk/sylvestre/lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}

* 35.0b4 looking like we'll do a build 2 with backout {{bug|1097321}} due to startup crash issues in b3

* Holiday Beta scheduling
** Week 3 - Dec 15-19: Beta 4 (Desktop & Mobile) and Beta 5 (Desktop) build & ship as usual
** Week 4 - Dec 22-26: Beta 6 (Desktop & Mobile) gtb on Monday Dec 22 as usual, ship on Tues Dec 23 - no further betas
** Week 5 - Dec 29-Jan 2: Beta 8 (Desktop & Mobile) gtb on Monday Dec 29 as usual, ship on Tues Dec 30 - no further betas
** Week 6 - Jan 5-9: Beta 10 (Mobile) and Desktop RC 35.0 gtb on Monday Jan 5th, ship on Tues Jan 6 to beta channels





===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)
* Tree Closing Window Saturday, Dec 20. Tentative time 0900-1730 PT, see {{bug|1111702|tracker}} for details.

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 2.29] (last week: 3.16).
* Many of the top oranges are lacking in action. I'll be pinging in bugs soon, please help if you can.
* 15 intermittent failures marked as fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2014-12-09&f1=cf_last_resolved&query_format=advanced&list_id=11734686 List] - Thanks!.
** Thanks to Andreas Pehrson from Telenor for fixing a frequent B2G assertion orange.

===CritSmash (dbolter)===








===MemShrink (njn)===


{{readonly}}


DMD now does [http://blog.mozilla.org/nnethercote/2014/12/11/cumulative-heap-profiling-in-firefox-with-dmd/ cumulative heap profiling]. This is great for finding places where excessive numbers of short-lived heap allocations occur.



===Stability (kairo)===








* Numbers look bad on desktop to some degree due to https://bugzilla.mozilla.org/show_bug.cgi?id=1097321#c26 (75% of all 35.0b3 crashes!)

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===
* All of this was announced in dev.platform and dev.b2g but here's your chance to ask questions
* PSA: You can now look your Try pushes to your custom mozharness repository (e.g. a user repo)
** [http://armenzg.blogspot.ca/2014/12/test-mozharness-changes-on-try.html Test mozharness changes on Try]
* Old news: You can easily run mozharness jobs on your machine (more support coming)
** [http://armenzg.blogspot.ca/2014/09/run-tbpl-jobs-locally-with-http.html Run mozharness jobs with --cfg developer_config.py]








===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Services (gps/lthomson)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===


{{readonly}}




* We're disabling WebSocket on Workers on beta because it's not stable enough.

===Electrolysis (e10s) (blassey)===








* Please help test e10s in Nightly!
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect
* {{bug|1092630}} landed. Should fix a host of problems on OSX related to plugins. Please test!

===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===








===GFX (milan)===








===JS (naveed)===

{{readonly}}
* 2015 Layout Roadmap posted:
** https://wiki.mozilla.org/Platform/Roadmap#JavaScript

===Layout (jet/dbaron)===


{{readonly}}
* 2015 Layout Roadmap posted:
** https://wiki.mozilla.org/Platform/Roadmap#Layout

===Media (mreavy)===


{{readonly}}

1. What has your team done since last week that might impact others?
* Landed rewrite of the webrtc call negotiation code - regressions are possible, some have been fixed
* Hello Rooms fixes have been uplifting to aurora and beta.

2. What will your team do this week that might impact others?
* Preparing to land webrtc.org import of stable branch 40 ({{bug|1109428}}) - same branch Chrome 40 will use.
** May well break --disable-webrtc builds again ;-) We'll fix it.
* k18e's team is planning to uplift some media rewrites being done by alfredo and blake wu.

3. Is anything slowing your team down or getting in their way?
* GMail/Gcal ;-)

===Necko (dougt/jduell)===




* HTTP/2 is scheduled to land on FF 35 (we'll advertise draft spec only)
** we'll advertise final (non-draft) HTTP/2 support in 36
** opportunistic encryption will be in 37

* B2G emulator still appears to be broken (pipe writes can get lost)
** we're trying to hack around it for our fix





===Performance (vladan)===



{{readonly}}

No update this week.





===Seceng (dougt)===








===Shumway (tschneidereit)===








===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

==Links==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
10:52 AM <KaiRo> lmandel: looks like I found the issue behind the gfx issues on beta, see https://bugzilla.mozilla.org/show_bug.cgi?id=1097321#c26
10:53 AM <KaiRo> and lsblakk ^^^
10:55 AM <lmandel> KaiRo: Good sleuthing.
10:56 AM <KaiRo> lmandel: luckily I just stumbled over bugmail of SoftVision verifying that bug that seems to have caused the issue ;-)
10:57 AM <KaiRo> and that got me thinking "hey, we did just land unblocking something that includes Intel stuff? wait a minute..." ;-)
11:00 AM <KaiRo> lsblakk: actually, 1) sheriffs/RyanVM can do a straight backout right away if we are sure enough, that doesn't even need Jeff, and 2) I'm actually reluctant to sign off 35.0b4 with this huge startup crash issue continued
11:00 AM <•lsblakk> ah, didn't see that it was a startup crash anywhere until now
11:00 AM <•lsblakk> in that case, i'm happy to take a backout and do a build 2
11:03 AM <overholt> cpeterson, did milan_ and I get disconnected?
11:03 AM <KaiRo> lsblakk: yes, took me a bit to realize as well, I'm definitely in favor of a build2 there.
11:04 AM <cpeterson> overholt: i don't see you guys on screen
11:04 AM <overholt> cpeterson, thanks. looks like a Vidyo crash. we're back.
11:04 AM <Pike> not just that the calendars are all upset, my head thinks it's wednesday, too
11:07 AM <RyanVM|sheriffduty> KaiRo: lsblakk: backing out now
11:07 AM <KaiRo> RyanVM|sheriffduty: thanks
11:10 AM <RyanVM|sheriffduty> jduell: CC me to that bug when you file it?
11:10 AM — RyanVM|sheriffduty wonders if that's the same underlying issue we have with other emulator test stability issues
11:11 AM <jduell> RyanVM|sheriffduty: will do
11:11 AM <RyanVM|sheriffduty> thanks
11:11 AM <jesup> jduell: sorry, we don't detect it directly: #if defined(MOZ_WIDGET_GONK) && defined(DEBUG) // B2G emulator debug is very, very slow and has problems dealing with realtime audio inputs
11:11 AM <jduell> jesup: ah. Ok, thanks
11:13 AM <jduell> jesup: hmm, this looks interesting... http://mxr.mozilla.org/mozilla-central/source/gfx/thebes/gfxAndroidPlatform.cpp#117
</pre>

Platform/Roadmap

2014-12-12T19:59:51Z

Naveed: /* JavaScript */ Initial 2015

=Teams=
==Accessibility==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Add info Here
* Another item here
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* More stuff
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* More stuff
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

==DOM==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Service Workers [Offline]
* IndexedDB in Workers [Offline]
* Picture Tag [Web Compatibility, Presto]
* requestSync (FxOS-only precursor to BackgroundSync) [Offline, Candle]
* TCP Socket in Workers [Offline]
* e10s (drag-and-drop, clipboard, leak detection and reporting)
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* BackgroundSync [Offline, Candle]
* Pre-rendering API [Presto]
* Shadow DOM [Web Compatibility]
* Custom Elements [Web Compatibility]
* Web Manifest [Web Compatibility]
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* Web Push [Offline, Candle, Web Compatibility]
* Image Resizing API [Candle, 60fps, MemShrink]
* Web Share primitive (towards Web Activities standardization) [Web Compatibility]
* finish remaining WebIDL conversions [CrashKill]
* JS-implemented plugins [CrashKill, Webify]
* IndexedDB data change observer events [Web Compatibility, Candle]
* localStorage + Quota Manager [FxOS feature enabler]
* FileSystem API [Web Compatibility]
* Media Control API [FxOS request]
* Device Orientation Locking (any spec work; others doing implementation) [Web Compatibility]
* Broadcast channel [Web Compatibility]
* Message Port [Web Compatibility]
* Remove appcache [Offline]
* Directory upload [Web Compatibility]
* DOM bits of Object.observe [Web Compatibility]
* Get rid of child array [MemShrink]
* WebGL in Workers [60fps]
* Web Audio in Workers [Web Compatibility]
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
|}

==e10s==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Add info Here
* Another item here
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* More stuff
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* More stuff
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

==Graphics==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* FirefoxOS GFX Device Support
* OMTC - Off Main Thead Compositing Windows
* e10s - Ship Electrolysis
* Project Silk
* Graphics - FirefoxOS Critical Memory Usage Reduction
* WebGL 2 GDC Demo
* Critical WebGL Desktop Peformance
* Desktop OOM driver related issues
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* APZ on Desktop
* Tiling on Desktop
* Desktop Scrolling Performance
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* APZ - "fake overscroll"
* APZ - OOP iframe support
* Zooming-in Improvements
* Overscroll Improvements
* Expose the graphics card details
* WebGL Mobile Performance
* WebGL Performance Parity on Desktop
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

==JavaScript==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Parsing and Caching Optimization Shumway [Presto, FlashKill]
* ARM Mobile Opts - Support GDC demo [FFOS, 60fps]
* Detailed GC jank Telemetry [MemShrink, 60fps]
* ES6 Classes [WebCompat]
* SAB GDC MWC demo [WebCompat, Presto, 60fps]
* SIMD.js GDC MWC demos [Presto, 60fps, WebCompat]
* ARM 64 baseline on Intel [FFOS]
* CGC Target release [MemShrink]
* JIT Frame for Profiler JIT Coach plumbing [DevTools]
* Experimental SIMD.js for ASM.js on x86 only (Intel demo) [WebCompat, Presto]
* ES6 Generators JITted [WebCompat, Presto]
* ES6 Symbols [WebCompat]
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* SIMD.js on ION Intel [Presto, 60fps, WebCompat]
* GC/CC scheduling improvements [MemShrink, 60fps]
* Shared Array Buffer v1 [WebCompat, Presto, 60fps]
* Research PGO [Presto, 60fps]
* Enable the backtracking allocator for all Ion code [Presto]
* Improve web framework (Shumway/Ember/Angular) performance [Presto, FlashKill]
* ES6 let and const [WebCompat]
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* JS team reduce jank (GC tuning) [60fps]
* SIMD.js on ION ARM [Presto, 60fps, WebCompat, FFOS]
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

==Layout==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Add info Here
* Another item here
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* More stuff
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* More stuff
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

==Media==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* MSE - Media Source Extensions (nightly)
* EME - Encrypted Media Extensions (nightly)
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* MSE (release)
* EME (release)
* Daala
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* MSE improvements
* EME continued development
* Video quality, performance and memory consumption
* MP4 demuxer written in Rust
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* This space intentionally left blank
|}

==Mobile Media==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Add info Here
* Another item here
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* More stuff
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* More stuff
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

==Mobile Platform==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Add info Here
* Another item here
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* More stuff
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* More stuff
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

==Networking==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Add info Here
* Another item here
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* More stuff
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* More stuff
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

==PKI==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Add info Here
* Another item here
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* More stuff
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* More stuff
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

==Sandboxing==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Add info Here
* Another item here
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* More stuff
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* More stuff
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

==Security==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Add info Here
* Another item here
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* More stuff
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* More stuff
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

==WebRTC / WebAudio==
 (All these features/fixes below are landing in Nightly during these quarters) 
{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Rewrite SDP/JSEP and add BUNDLE support
* Multistream, renegotiation support
* VP9 codec support in WebRTC
* Web Audio and WebRTC working well together
* e10s problems fixed
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* OpenH264 for Android working well
* Audio workers
* Web Audio performance improvements
* Simulcast
* All echo and audio problems in WebRTC 1:1 calls resolved
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* getUserMedia and audio output sandboxing working
* Considerably better NAT traversal (including ICE proxy and UPnP support)
* Audio output selection
* Data channels in workers
* Compliant with "v1.0" (or equivalent) of the WebRTC spec

------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

==Games==

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Current Plans !! style="text-align: center;" width: "50%;" | Previous Plans
|-
| style="vertical-align:top;" |
* Testing & Benchmarks
** Collaborate with QA to develop a regular cadence for running benchmarks + analysis
** Collaborate with QA to develop a "games test plan" for each release cycle
** Reporting: create a mechanism for reporting the above to incite action on part of engineering
------ Items above planned to be done throughout 2015 ------
* GDC 2015 {{bug|1107589}}
** Technical areas of focus include include: Polish & Performance, WebVR, pthreads, SIMD, WebGL2, and possibly Web Audio
** Identify all Demo Content and continue to define technical requirements
** Work with PR to identify campaign messaging, demo deliverables and related schedule
** Pre-event hardware requirements, training, and attendance logistics
* Win64: confirm and communicate schedule
* Emerge from Q1 with a solid plan for triage going forward
------ Items above planned to be done before or during Gecko 39 (Q1) ------
* In progress
------ Items above planned to be done before or during Gecko 42 (Q2) ------
* In progress
------ Items above planned to be done before or during Gecko 45 (End 2015) ------
| style="vertical-align:top;" |
* Nothing here for now.
|}

=Initatives=

* 60fps
** Focused on producing a smooth, jank free experiences. 60fps goal is dependant on media type.
* BarrierSmash
** Insure that accessibility features are working throughout our products.
* Candle
** Program targeted at reducing energy usage.
* CrashKill
** Improve the overall stability of Gecko and the project that rely on it.
* CritSmash
** Fix known critical security bugs.
* Electrolysis
** This is focused on providing multi processor tab support and another name for e10s.
* Offline
** Offline Support
* Presto
** Program targeted at improving overall load times and performance. This is resurrecting an older program that was discontinued.
* MemShrink
**Reduce memory usage (all products)
* Web Compatibility
** Improve the overall web compatibility of Gecko.
* Webify
** Reduce the webs dependence on plugins. This includes several content targeted initiatives such as the games program (Unity), Shumway (Flash), MSE/EME (Flash/Netflix), WebRTC (Google Talk, Facebook Video)

[[Category:Roadmaps]]

Platform/2014-12-09

2014-12-09T19:03:59Z

Naveed: /* JS (naveed) */

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lsblakk/sylvestre/lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}


* Firefox 34.0.5 updates are enabled at 100% as of this morning
* We might need to do a mobile-only 34.0.1
* Firefox Beta 35.0b2 shipping today
* Fennec Beta 35.0b2 delayed go to build until Thursday
** We're still working on split apk for Gingerbread users, should have that in place in the next couple of weeks



===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===








===CritSmash (dbolter)===








===MemShrink (njn)===


{{readonly}}
No update.





===Stability (kairo)===








==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===








===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Services (gps/lthomson)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===








===Electrolysis (e10s) (blassey)===








* Please help test e10s in Nightly!
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect

===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===








===GFX (milan)===

* B2G: the follow up to 2.1 ("2.X") looks to be based on Gecko 37...
** Graphics plans are unchanged from 2.2 to 2.X
** Graphics plans were based on Gecko 38
** So... will likely keep the 38 time frame and uplift to B2G 37 branch past the trunk. Will figure it out by mid January when this becomes relevant.

===JS (naveed)===





* Work Week
** Shumway load time is highest priority
** 2015 Planning (more on this to come)

===Layout (jet/dbaron)===


{{readonly}}

* Investigating {{bug|1107378}} to fix webkit-dependent sites in China added to a mobile (fennec) fix-list.
* Landed {{bug|1089417}} - restyling fixes for CSS media queries

===Media (mreavy)===


{{readonly}}

* 1. What has your team done since last week that might impact others?
** Hello is in Release/34! Early reviews are generally good (and recognize the differences for privacy compared to say Skype).
** Landed sdparta! {{bug|1091242}} - (rewrite of the majority of webrtc signaling, other than the parsing).
*** Known regression {{bug|1109130}} breaks < MSVC 2013 compiles; fix shortly
** Lots of great discussions at #mozlandia
** FoxEye presentation (echoes of roc's older MediaStream Processing proposal)
** Work moving forward towards multiple streams of a type and renegotiation
* 2. What will your team do this week that might impact others? -->
** Starting work towards a webrtc.org update
** More sdparta work



===Necko (dougt/jduell)===








===Performance (vladan)===




1. What has your team done since last week that might impact others?

* {{bug|1107779}}, {{bug|1107782}}: Avi found that the "activeTicks" FHR measurement significantly over-reports Firefox usage time, because it fires "user-interaction-active" notifications while the mouse cursor is positioned over the browser even when the user is away from the computer
** Should we just land the fix, or is it important to maintain continuity with the current measurement (for monitoring for relative changes)?
** The above bugs are unrelated to the big drop in activeTicks reported in {{bug|1096498}}
* Talos numbers for most E10s tests are available
** we're still converting some tests, e.g. tresize
** there are serious regressions from E10S, e.g. WebGL is [http://graphs.mozilla.org/graph.html#tests=%5B%5B325,1,41%5D,%5B325,1,47%5D,%5B325,1,33%5D,%5B325,1,25%5D%5D&sel=none&displayrange=30&datatype=running 4x worse on Windows]
** Joel Maher said he'll write a blog post summarizing Talos regressions/improvements from E10S
* Spark is the new, much faster way of analyzing large amounts of Telemetry data:
** http://robertovitillo.com/2014/11/29/a-telemetry-api-for-spark/
** www.slideshare.net/RobertoAgostinoVitil/spark-meets-telemetry

2. What will your team do this week that might impact others?

* {{bug|998863}}: Almost ready to land asynchronous initialization of out-of-process plugins

3. Is anything slowing your team down or getting in their way?

* {{bug|998863}}: Need one more review for asynchronous initialization of out-of-process plugins

===Seceng (dougt)===








===Shumway (tschneidereit)===





* As part of the FlashKill initiative, the Shumway team's Q1 goal is to whitelist Shumway for Facebook's Flash Video Player:
** https://wiki.mozilla.org/Shumway/Roadmap#FB1_Milestone
** Facebook test videos: https://www.facebook.com/gopro/videos
* Working with JS team on JS startup performance and Media team on video buffering.

===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

=== Touch input standardization update (mbrubeck) ===

* [http://www.w3.org/TR/pointerevents/ W3C Pointer Events] going to Proposed Rec. Shipping in IE, portions shipping in Chrome, partially implemented in Gecko.
** Chrome and Safari have no plans to ship full Pointer Events implementation.
* [http://www.w3.org/community/touchevents/ Touch Events CG] is actively discussing errata and extensions, about to start a weekly-ish telecon. Let me know if you want to get involved.
* '''[[Gecko/Touch]]''' has a breakdown of our implementation status and various missing pieces.

==<Read only beyond this point>==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)
* '''"Mastering Version Control at Mozilla"''' (Gregory Szorc)
** https://people.mozilla.org/~gszorc/mastering-vcs/
* '''"How Microsoft Uses C++ to Deliver Office Across iOS, Android, Windows, and Mac"''' (CppCon 2014 video)
** Part 1: https://www.youtube.com/watch?v=3HROqnw-nf4 (one hour)
** Part 2: https://www.youtube.com/watch?v=MGMoRu5yrVc (one hour)
* '''"Emscripten and asm.js: C++'s role in the modern web"''' (CppCon 2014 video with Mozilla's own Alon Zakai)
** https://www.youtube.com/watch?v=JhMlWj4tCDo (one hour)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2014-12-09

2014-12-09T19:02:29Z

Naveed: /* JS (naveed) */

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lsblakk/sylvestre/lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}


* Firefox 34.0.5 updates are enabled at 100% as of this morning
* We might need to do a mobile-only 34.0.1
* Firefox Beta 35.0b2 shipping today
* Fennec Beta 35.0b2 delayed go to build until Thursday
** We're still working on split apk for Gingerbread users, should have that in place in the next couple of weeks



===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===








===CritSmash (dbolter)===








===MemShrink (njn)===


{{readonly}}
No update.





===Stability (kairo)===








==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===








===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Services (gps/lthomson)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===








===Electrolysis (e10s) (blassey)===








* Please help test e10s in Nightly!
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect

===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===








===GFX (milan)===

* B2G: the follow up to 2.1 ("2.X") looks to be based on Gecko 37...
** Graphics plans are unchanged from 2.2 to 2.X
** Graphics plans were based on Gecko 38
** So... will likely keep the 38 time frame and uplift to B2G 37 branch past the trunk. Will figure it out by mid January when this becomes relevant.

===JS (naveed)===


{{readonly}}





* Work Week
** Shumway load time is highest priority
** 2015 Planning (more on this to come)

===Layout (jet/dbaron)===


{{readonly}}

* Investigating {{bug|1107378}} to fix webkit-dependent sites in China added to a mobile (fennec) fix-list.
* Landed {{bug|1089417}} - restyling fixes for CSS media queries

===Media (mreavy)===


{{readonly}}

* 1. What has your team done since last week that might impact others?
** Hello is in Release/34! Early reviews are generally good (and recognize the differences for privacy compared to say Skype).
** Landed sdparta! {{bug|1091242}} - (rewrite of the majority of webrtc signaling, other than the parsing).
*** Known regression {{bug|1109130}} breaks < MSVC 2013 compiles; fix shortly
** Lots of great discussions at #mozlandia
** FoxEye presentation (echoes of roc's older MediaStream Processing proposal)
** Work moving forward towards multiple streams of a type and renegotiation
* 2. What will your team do this week that might impact others? -->
** Starting work towards a webrtc.org update
** More sdparta work



===Necko (dougt/jduell)===








===Performance (vladan)===








===Seceng (dougt)===








===Shumway (tschneidereit)===





* As part of the FlashKill initiative, the Shumway team's Q1 goal is to whitelist Shumway for Facebook's Flash Video Player:
** https://wiki.mozilla.org/Shumway/Roadmap#FB1_Milestone
** Facebook test videos: https://www.facebook.com/gopro/videos
* Working with JS team on JS startup performance and Media team on video buffering.

===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

=== Touch input standardization update (mbrubeck) ===

* [http://www.w3.org/TR/pointerevents/ W3C Pointer Events] going to Proposed Rec. Shipping in IE, portions shipping in Chrome, partially implemented in Gecko.
** Chrome and Safari have no plans to ship full Pointer Events implementation.
* [http://www.w3.org/community/touchevents/ Touch Events CG] is actively discussing errata and extensions, about to start a weekly-ish telecon. Let me know if you want to get involved.
* '''[[Gecko/Touch]]''' has a breakdown of our implementation status and various missing pieces.

==<Read only beyond this point>==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)
* '''"Mastering Version Control at Mozilla"''' (Gregory Szorc)
** https://people.mozilla.org/~gszorc/mastering-vcs/
* '''"How Microsoft Uses C++ to Deliver Office Across iOS, Android, Windows, and Mac"''' (CppCon 2014 video)
** Part 1: https://www.youtube.com/watch?v=3HROqnw-nf4 (one hour)
** Part 2: https://www.youtube.com/watch?v=MGMoRu5yrVc (one hour)
* '''"Emscripten and asm.js: C++'s role in the modern web"''' (CppCon 2014 video with Mozilla's own Alon Zakai)
** https://www.youtube.com/watch?v=JhMlWj4tCDo (one hour)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2014-11-04

2014-11-04T19:10:04Z

Naveed: /* JS (naveed) */ bugzillaified links

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}





* possible 33.0.3 for further gfx/stability fixes
* 34 beta6 desktop shipped today
* 34 beta6 mobile should ship tomorrow

* 33.1 build3 likely coming

* Next beta go to build
** desktop: beta7 Thu
** mobile/desktop: beta8 Mon
* Next week is the last week for beta builds. Still [https://bugzilla.mozilla.org/buglist.cgi?v4=---&f1=cf_tracking_firefox34&o3=equals&v3=affected&j2=OR&o1=equals&f4=cf_status_firefox34&query_format=advanced&f3=cf_status_firefox34&o4=equals&f2=OP&v1=%2B&list_id=11497575 ~70 tracked bugs]. Get your fixes in!

===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)
{{readonly}}
* Tree Closing Window on Saturday, November 8. {{bug|1087431}} is the tracker.
** ''The November 1 window reported last week was postponed to avoid conflicts with decade builds. Final notice is given to the dev groups when everything is "go".''
** An unusually long window -- approx 11-1/2 hours.
** Most of the work is network related, with interruptions in traffic from time to time.
** We'll leave trees "open", but developers should expect longer than normal build times and potential need to restart some jobs.

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===
{{readonly}}
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 8.38] (last week: 7.77).
* e10s testing is an ongoing source of pain. I disabled a number of top oranges in the last week trying to get them stable.
* 33 intermittent failures marked as fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2014-10-28&f1=cf_last_resolved&query_format=advanced&list_id=11501811 List] - Thanks!.

===CritSmash (dbolter)===








===MemShrink (njn)===


{{readonly}}




Please [http://blog.mozilla.org/nnethercote/2014/11/04/please-grow-your-buffers-exponentially/ grow your buffers exponentially]. It reduces heap churn and fragmentation.

===Stability (kairo)===
{{readonly}}

Bugs needing attention (all GFX, in order of priority):
* 33 Release: startup crashes {{bug|1021265}}, potentially uplift for {{bug|1064107}}
* 34 beta mobile: {{bug|1049138}}
* 35 Aurora: {{bug|1091903}}
* 36 Nightly: {{bug|1089364}}

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===


{{readonly}}

'''Blog and newsgroups posts'''
* [gbrown] [http://gbrownmozilla.wordpress.com/2014/10/31/firefox-for-android-performance-measures-septemberoctober-check-up-2/ Firefox for Android Performance Measures]
* [jmaher] [http://elvis314.wordpress.com/2014/10/30/a-case-of-the-weekends/ A case of the weekends?]





===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Services (gps/lthomson)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===








===Electrolysis (e10s) (blassey)===


* Add-on performance, printing, and plugins have improved over the past week.


* We plan to enable e10s by default for Nightly users this week! \o/
** except people using IME or a11y
** To opt-in now, open "Preferences" and check the "Enable E10S (multi-process)" checkbox.
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect



===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===



====Done since last week that might impact others====
* worked on Reader mode/reading list
====Doing this week that might impact others====
* continuing work on reader mode/reading list
* discussions underway with Desktop and Cloud Services on Password Management
====Working on that is dependent on others====
* Splitting APK - next steps are with RelEng
* Disabling OCSP in Firefox for Android
* Surfacing new 'Firefox Account Locked' messaging - awaiting input from Cloud Services

===GFX (milan)===

* Ongoing graphics driver/hardware related issues being looked at in the release (33) channel. This is having a negative impact on looking at the beta tracked issues.

* Second round of graphics planning. With input from desktop and date changes from Firefox OS, here is the updated list of priorities:

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Previous Plans !! style="text-align: center;" width: "50%;" | Current Plans
|-
|
* Firefox OS 2.0 & 2.1 blockers
* E10S support (OMTC)
* Firefox OS memory usage reduction
* Project Silk support
** Scrolling physics + v-sync
* APZ improvements
** OOP support
** fake overscroll
* WebGL desktop performance (critical items)
* WebGL mobile performance
------ Line for Gecko 39/2.2/GDC/MWC ------
* OMTC everywhere
* APZ on desktop
* Tiling on desktop
------ Line for Gecko 41 ------
* Skia canvas
* WebGL performance parity on desktop
------ Line for Gecko 43 ------
* Skia content
* Multi-threaded content painting
------ Line for Gecko 45 ------
------ Line for 2015 ------
|
* Firefox OS 2.0 & 2.1 blockers
* (new) Firefox OS 2.2 on Android Lollipop
* E10S support (OMTC)
* ↓ Firefox OS memory usage reduction (minimal)
* Project Silk support
** Scrolling physics + v-sync
------ Line for Gecko 38/2.2 ------
* WebGL2 support + demo
* WebGL desktop performance (critical items)
* (new) Desktop OOM driver related issues
------ Line for Gecko 39/GDC ------
* OMTC everywhere
* APZ on desktop
* Tiling on desktop
* (new) Desktop scrolling performance
------ Line for Gecko 41 ------
* ↓ APZ improvements
** OOP support
** fake overscroll
* ↓ WebGL mobile performance
* ↓ Skia canvas
* ↓ WebGL performance parity on desktop
------ Line for Gecko 44 ------
------ Line for 2015 ------
* ↓ Skia content
* ↓ Multi-threaded content painting
|
|}

===JS (naveed)===


{{readonly}}

* THIS WEEK
**{{bug|1087468}}: We still have regressions we the inlining of any for-loop, still looking at the NavierStokes improvement, I was able to isolated a better patch which give us ~22.5% improvement on NavierStokes, without regressing other benchmarks.
** Compacting GC ({{bug|650161}}) Compacting shell tests are now enabled on inbound
** Only perform a minor GC when the store buffer is full ({{bug|1089582}})
** Landed new memory organization for non-native objects ({{bug|1073842}})
** {{bug|979594 }} (Atomics for plain JS): Landed, at last

* THIS WEEK AFFECT OTHERS
** Land the asm.js and DOM parts of Atomics

* SLOWING US DOWN
** n/a

=== Emscripten (naveed)===

* Updated emscripten unit test system to run on nightly, aurora and beta [http://clb.demon.fi:8112/waterfall test results]
** Uncovered a number of regressions in the dev channels
*** These have all (or almost all) been filed. Let us know if you need any assistance replicating the issues

===Layout (jet/dbaron)===


{{readonly}}

* Platform-wide business planning last week and this week.
* Minor updates to Q4 [[Platform/2014-Q4-Goals#Layout|Layout goals]]

===Media (mreavy)===


{{readonly}}


* Found major perf issue on B2G caused by --- the network activity status anim! {{Bug|1091240}} and follow-ons.
** Caused 20-30% CPU use and multi-second network latency in some cases. Wallpaper fix is to reduce frame rate to 5-6FPS from 30fps (and the anim had ~5 duplicates of each frame anyways, so that doesn't even change the visual)
** Dramatically improves Hello on B2G; also helps with fetching larger amounts of content/PDFs/images.
* Fixed getUserMedia regression (delay) on Mac audio when switching outputs (like plugging in earbuds) due to bug 848954 on OSX 10.6-10.9
** Found that Yosemite (10.10) has broken this (and output panning to right speaker to avoid mic on top of left speaker)
* Progress towards using Promises with getUserMedia/CreateOffer/etc at TPAC last week


* Hope to land fix for 3 top WebRTC oranges today



===Necko (dougt/jduell)===




* B2G emulator perma-oranges: ran on desktop emulator and didn't see timeout, so we're blaming on hardware and disabling tests for now.
* fixed topcrasher (Avast HTTP scanning prevented shutdown) ({{bug|1087674}})
* Upgrading to v15 of the HTTP/2 spec.
* OpenVPN API is getting close. Unclear how soon we'll get UI/webAPI done ({{bug|1033580}})





===Performance (vladan)===








===Seceng (dougt)===








===Shumway (tschneidereit)===








===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

==<Read only beyond this point>==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)
* [https://play.google.com/store/apps/details?id=at.paul.firefoxwidget
Firefox Countdown Widget] for your Android home screen

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2014-11-04

2014-11-04T19:06:12Z

Naveed: /* Emscripten (naveed) */ ad

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}





* possible 33.0.3 for further gfx/stability fixes
* 34 beta6 desktop shipped today
* 34 beta6 mobile should ship tomorrow

* 33.1 build3 likely coming

* Next beta go to build
** desktop: beta7 Thu
** mobile/desktop: beta8 Mon
* Next week is the last week for beta builds. Still ~70 tracked bugs. Get your fixes in!

===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)
{{readonly}}
* Tree Closing Window on Saturday, November 8. {{bug|1087431}} is the tracker.
** ''The November 1 window reported last week was postponed to avoid conflicts with decade builds. Final notice is given to the dev groups when everything is "go".''
** An unusually long window -- approx 11-1/2 hours.
** Most of the work is network related, with interruptions in traffic from time to time.
** We'll leave trees "open", but developers should expect longer than normal build times and potential need to restart some jobs.

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===
{{readonly}}
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 8.38] (last week: 7.77).
* e10s testing is an ongoing source of pain. I disabled a number of top oranges in the last week trying to get them stable.
* 33 intermittent failures marked as fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2014-10-28&f1=cf_last_resolved&query_format=advanced&list_id=11501811 List] - Thanks!.

===CritSmash (dbolter)===








===MemShrink (njn)===


{{readonly}}




Please [http://blog.mozilla.org/nnethercote/2014/11/04/please-grow-your-buffers-exponentially/ grow your buffers exponentially]. It reduces heap churn and fragmentation.

===Stability (kairo)===
{{readonly}}

Bugs needing attention (all GFX, in order of priority):
* 33 Release: startup crashes {{bug|1021265}}, potentially uplift for {{bug|1064107}}
* 34 beta mobile: {{bug|1049138}}
* 35 Aurora: {{bug|1091903}}
* 36 Nightly: {{bug|1089364}}

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===


{{readonly}}

'''Blog and newsgroups posts'''
* [gbrown] [http://gbrownmozilla.wordpress.com/2014/10/31/firefox-for-android-performance-measures-septemberoctober-check-up-2/ Firefox for Android Performance Measures]
* [jmaher] [http://elvis314.wordpress.com/2014/10/30/a-case-of-the-weekends/ A case of the weekends?]





===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Services (gps/lthomson)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===








===Electrolysis (e10s) (blassey)===


* Add-on performance, printing, and plugins have improved over the past week.


* We plan to enable e10s by default for Nightly users this week! \o/
** except people using IME or a11y
** To opt-in now, open "Preferences" and check the "Enable E10S (multi-process)" checkbox.
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect



===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===



====Done since last week that might impact others====
* worked on Reader mode/reading list
====Doing this week that might impact others====
* continuing work on reader mode/reading list
* discussions underway with Desktop and Cloud Services on Password Management
====Working on that is dependent on others====
* Splitting APK - next steps are with RelEng
* Disabling OCSP in Firefox for Android
* Surfacing new 'Firefox Account Locked' messaging - awaiting input from Cloud Services

===GFX (milan)===

* Ongoing graphics driver/hardware related issues being looked at in the release (33) channel. This is having a negative impact on looking at the beta tracked issues.

* Second round of graphics planning. With input from desktop and date changes from Firefox OS, here is the updated list of priorities:

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Previous Plans !! style="text-align: center;" width: "50%;" | Current Plans
|-
|
* Firefox OS 2.0 & 2.1 blockers
* E10S support (OMTC)
* Firefox OS memory usage reduction
* Project Silk support
** Scrolling physics + v-sync
* APZ improvements
** OOP support
** fake overscroll
* WebGL desktop performance (critical items)
* WebGL mobile performance
------ Line for Gecko 39/2.2/GDC/MWC ------
* OMTC everywhere
* APZ on desktop
* Tiling on desktop
------ Line for Gecko 41 ------
* Skia canvas
* WebGL performance parity on desktop
------ Line for Gecko 43 ------
* Skia content
* Multi-threaded content painting
------ Line for Gecko 45 ------
------ Line for 2015 ------
|
* Firefox OS 2.0 & 2.1 blockers
* E10S support (OMTC)
* ↓ Firefox OS memory usage reduction (minimal)
* Project Silk support
** Scrolling physics + v-sync
------ Line for Gecko 38/2.2 ------
* WebGL2 support + demo
* WebGL desktop performance (critical items)
* (new) Desktop OOM driver related issues
------ Line for Gecko 39/GDC ------
* OMTC everywhere
* APZ on desktop
* Tiling on desktop
* (new) Desktop scrolling performance
------ Line for Gecko 41 ------
* ↓ APZ improvements
** OOP support
** fake overscroll
* ↓ WebGL mobile performance
* ↓ Skia canvas
* ↓ WebGL performance parity on desktop
------ Line for Gecko 44 ------
------ Line for 2015 ------
* ↓ Skia content
* ↓ Multi-threaded content painting
|
|}

===JS (naveed)===


{{readonly}}

* THIS WEEK
**Bug 1087468: We still have regressions we the inlining of any for-loop, still looking at the NavierStokes improvement, I was able to isolated a better patch which give us ~22.5% improvement on NavierStokes, without regressing other benchmarks.
** Compacting GC (bug 650161) Compacting shell tests are now enabled on inbound
** Only perform a minor GC when the store buffer is full (bug 1089582)
** Landed new memory organization for non-native objects (bug 1073842)
** Bug 979594 (Atomics for plain JS): Landed, at last

* THIS WEEK AFFECT OTHERS
** Land the asm.js and DOM parts of Atomics

* SLOWING US DOWN
** n/a

=== Emscripten (naveed)===

* Updated emscripten unit test system to run on nightly, aurora and beta [http://clb.demon.fi:8112/waterfall test results]
** Uncovered a number of regressions in the dev channels
*** These have all (or almost all) been filed. Let us know if you need any assistance replicating the issues

===Layout (jet/dbaron)===


{{readonly}}

* Platform-wide business planning last week and this week.
* Minor updates to Q4 [[Platform/2014-Q4-Goals#Layout|Layout goals]]

===Media (mreavy)===


{{readonly}}


* Found major perf issue on B2G caused by --- the network activity status anim! {{Bug|1091240}} and follow-ons.
** Caused 20-30% CPU use and multi-second network latency in some cases. Wallpaper fix is to reduce frame rate to 5-6FPS from 30fps (and the anim had ~5 duplicates of each frame anyways, so that doesn't even change the visual)
** Dramatically improves Hello on B2G; also helps with fetching larger amounts of content/PDFs/images.
* Fixed getUserMedia regression (delay) on Mac audio when switching outputs (like plugging in earbuds) due to bug 848954 on OSX 10.6-10.9
** Found that Yosemite (10.10) has broken this (and output panning to right speaker to avoid mic on top of left speaker)
* Progress towards using Promises with getUserMedia/CreateOffer/etc at TPAC last week


* Hope to land fix for 3 top WebRTC oranges today



===Necko (dougt/jduell)===




* B2G emulator perma-oranges: ran on desktop emulator and didn't see timeout, so we're blaming on hardware and disabling tests for now.
* fixed topcrasher (Avast HTTP scanning prevented shutdown) ({{bug|1087674}})
* Upgrading to v15 of the HTTP/2 spec.
* OpenVPN API is getting close. Unclear how soon we'll get UI/webAPI done ({{bug|1033580}})





===Performance (vladan)===








===Seceng (dougt)===








===Shumway (tschneidereit)===








===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

==<Read only beyond this point>==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2014-11-04

2014-11-04T19:05:56Z

Naveed: /* JS (naveed) */ aa

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}





* possible 33.0.3 for further gfx/stability fixes
* 34 beta6 desktop shipped today
* 34 beta6 mobile should ship tomorrow

* 33.1 build3 likely coming

* Next beta go to build
** desktop: beta7 Thu
** mobile/desktop: beta8 Mon
* Next week is the last week for beta builds. Still ~70 tracked bugs. Get your fixes in!

===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)
{{readonly}}
* Tree Closing Window on Saturday, November 8. {{bug|1087431}} is the tracker.
** ''The November 1 window reported last week was postponed to avoid conflicts with decade builds. Final notice is given to the dev groups when everything is "go".''
** An unusually long window -- approx 11-1/2 hours.
** Most of the work is network related, with interruptions in traffic from time to time.
** We'll leave trees "open", but developers should expect longer than normal build times and potential need to restart some jobs.

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===
{{readonly}}
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 8.38] (last week: 7.77).
* e10s testing is an ongoing source of pain. I disabled a number of top oranges in the last week trying to get them stable.
* 33 intermittent failures marked as fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2014-10-28&f1=cf_last_resolved&query_format=advanced&list_id=11501811 List] - Thanks!.

===CritSmash (dbolter)===








===MemShrink (njn)===


{{readonly}}




Please [http://blog.mozilla.org/nnethercote/2014/11/04/please-grow-your-buffers-exponentially/ grow your buffers exponentially]. It reduces heap churn and fragmentation.

===Stability (kairo)===
{{readonly}}

Bugs needing attention (all GFX, in order of priority):
* 33 Release: startup crashes {{bug|1021265}}, potentially uplift for {{bug|1064107}}
* 34 beta mobile: {{bug|1049138}}
* 35 Aurora: {{bug|1091903}}
* 36 Nightly: {{bug|1089364}}

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===


{{readonly}}

'''Blog and newsgroups posts'''
* [gbrown] [http://gbrownmozilla.wordpress.com/2014/10/31/firefox-for-android-performance-measures-septemberoctober-check-up-2/ Firefox for Android Performance Measures]
* [jmaher] [http://elvis314.wordpress.com/2014/10/30/a-case-of-the-weekends/ A case of the weekends?]





===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Services (gps/lthomson)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===








===Electrolysis (e10s) (blassey)===


* Add-on performance, printing, and plugins have improved over the past week.


* We plan to enable e10s by default for Nightly users this week! \o/
** except people using IME or a11y
** To opt-in now, open "Preferences" and check the "Enable E10S (multi-process)" checkbox.
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect



===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===



====Done since last week that might impact others====
* worked on Reader mode/reading list
====Doing this week that might impact others====
* continuing work on reader mode/reading list
* discussions underway with Desktop and Cloud Services on Password Management
====Working on that is dependent on others====
* Splitting APK - next steps are with RelEng
* Disabling OCSP in Firefox for Android
* Surfacing new 'Firefox Account Locked' messaging - awaiting input from Cloud Services

===GFX (milan)===

* Ongoing graphics driver/hardware related issues being looked at in the release (33) channel. This is having a negative impact on looking at the beta tracked issues.

* Second round of graphics planning. With input from desktop and date changes from Firefox OS, here is the updated list of priorities:

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Previous Plans !! style="text-align: center;" width: "50%;" | Current Plans
|-
|
* Firefox OS 2.0 & 2.1 blockers
* E10S support (OMTC)
* Firefox OS memory usage reduction
* Project Silk support
** Scrolling physics + v-sync
* APZ improvements
** OOP support
** fake overscroll
* WebGL desktop performance (critical items)
* WebGL mobile performance
------ Line for Gecko 39/2.2/GDC/MWC ------
* OMTC everywhere
* APZ on desktop
* Tiling on desktop
------ Line for Gecko 41 ------
* Skia canvas
* WebGL performance parity on desktop
------ Line for Gecko 43 ------
* Skia content
* Multi-threaded content painting
------ Line for Gecko 45 ------
------ Line for 2015 ------
|
* Firefox OS 2.0 & 2.1 blockers
* E10S support (OMTC)
* ↓ Firefox OS memory usage reduction (minimal)
* Project Silk support
** Scrolling physics + v-sync
------ Line for Gecko 38/2.2 ------
* WebGL2 support + demo
* WebGL desktop performance (critical items)
* (new) Desktop OOM driver related issues
------ Line for Gecko 39/GDC ------
* OMTC everywhere
* APZ on desktop
* Tiling on desktop
* (new) Desktop scrolling performance
------ Line for Gecko 41 ------
* ↓ APZ improvements
** OOP support
** fake overscroll
* ↓ WebGL mobile performance
* ↓ Skia canvas
* ↓ WebGL performance parity on desktop
------ Line for Gecko 44 ------
------ Line for 2015 ------
* ↓ Skia content
* ↓ Multi-threaded content painting
|
|}

===JS (naveed)===


{{readonly}}

* THIS WEEK
**Bug 1087468: We still have regressions we the inlining of any for-loop, still looking at the NavierStokes improvement, I was able to isolated a better patch which give us ~22.5% improvement on NavierStokes, without regressing other benchmarks.
** Compacting GC (bug 650161) Compacting shell tests are now enabled on inbound
** Only perform a minor GC when the store buffer is full (bug 1089582)
** Landed new memory organization for non-native objects (bug 1073842)
** Bug 979594 (Atomics for plain JS): Landed, at last

* THIS WEEK AFFECT OTHERS
** Land the asm.js and DOM parts of Atomics

* SLOWING US DOWN
** n/a

=== Emscripten (naveed)===
{{readonly}}

* Updated emscripten unit test system to run on nightly, aurora and beta [http://clb.demon.fi:8112/waterfall test results]
** Uncovered a number of regressions in the dev channels
*** These have all (or almost all) been filed. Let us know if you need any assistance replicating the issues

===Layout (jet/dbaron)===


{{readonly}}

* Platform-wide business planning last week and this week.
* Minor updates to Q4 [[Platform/2014-Q4-Goals#Layout|Layout goals]]

===Media (mreavy)===


{{readonly}}


* Found major perf issue on B2G caused by --- the network activity status anim! {{Bug|1091240}} and follow-ons.
** Caused 20-30% CPU use and multi-second network latency in some cases. Wallpaper fix is to reduce frame rate to 5-6FPS from 30fps (and the anim had ~5 duplicates of each frame anyways, so that doesn't even change the visual)
** Dramatically improves Hello on B2G; also helps with fetching larger amounts of content/PDFs/images.
* Fixed getUserMedia regression (delay) on Mac audio when switching outputs (like plugging in earbuds) due to bug 848954 on OSX 10.6-10.9
** Found that Yosemite (10.10) has broken this (and output panning to right speaker to avoid mic on top of left speaker)
* Progress towards using Promises with getUserMedia/CreateOffer/etc at TPAC last week


* Hope to land fix for 3 top WebRTC oranges today



===Necko (dougt/jduell)===




* B2G emulator perma-oranges: ran on desktop emulator and didn't see timeout, so we're blaming on hardware and disabling tests for now.
* fixed topcrasher (Avast HTTP scanning prevented shutdown) ({{bug|1087674}})
* Upgrading to v15 of the HTTP/2 spec.
* OpenVPN API is getting close. Unclear how soon we'll get UI/webAPI done ({{bug|1033580}})





===Performance (vladan)===








===Seceng (dougt)===








===Shumway (tschneidereit)===








===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

==<Read only beyond this point>==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2014-11-04

2014-11-04T19:03:33Z

Naveed: /* JS (naveed) */ a

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}





* possible 33.0.3 for further gfx/stability fixes
* 34 beta6 desktop shipped today
* 34 beta6 mobile should ship tomorrow

* 33.1 build3 likely coming

* Next beta go to build
** desktop: beta7 Thu
** mobile/desktop: beta8 Mon
* Next week is the last week for beta builds. Still ~70 tracked bugs. Get your fixes in!

===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)
{{readonly}}
* Tree Closing Window on Saturday, November 8. {{bug|1087431}} is the tracker.
** ''The November 1 window reported last week was postponed to avoid conflicts with decade builds. Final notice is given to the dev groups when everything is "go".''
** An unusually long window -- approx 11-1/2 hours.
** Most of the work is network related, with interruptions in traffic from time to time.
** We'll leave trees "open", but developers should expect longer than normal build times and potential need to restart some jobs.

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===
{{readonly}}
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 8.38] (last week: 7.77).
* e10s testing is an ongoing source of pain. I disabled a number of top oranges in the last week trying to get them stable.
* 33 intermittent failures marked as fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2014-10-28&f1=cf_last_resolved&query_format=advanced&list_id=11501811 List] - Thanks!.

===CritSmash (dbolter)===








===MemShrink (njn)===


{{readonly}}




Please [http://blog.mozilla.org/nnethercote/2014/11/04/please-grow-your-buffers-exponentially/ grow your buffers exponentially]. It reduces heap churn and fragmentation.

===Stability (kairo)===








==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===


{{readonly}}

'''Blog and newsgroups posts'''
* [gbrown] [http://gbrownmozilla.wordpress.com/2014/10/31/firefox-for-android-performance-measures-septemberoctober-check-up-2/ Firefox for Android Performance Measures]
* [jmaher] [http://elvis314.wordpress.com/2014/10/30/a-case-of-the-weekends/ A case of the weekends?]





===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Services (gps/lthomson)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===








===Electrolysis (e10s) (blassey)===


* Add-on performance, printing, and plugins have improved over the past week.


* We plan to enable e10s by default for Nightly users this week! \o/
** except people using IME or a11y
** To opt-in now, open "Preferences" and check the "Enable E10S (multi-process)" checkbox.
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect



===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===



====Done since last week that might impact others====
* worked on Reader mode/reading list
====Doing this week that might impact others====
* continuing work on reader mode/reading list
* discussions underway with Desktop and Cloud Services on Password Management
====Working on that is dependent on others====
* Splitting APK - next steps are with RelEng
* Disabling OCSP in Firefox for Android
* Surfacing new 'Firefox Account Locked' messaging - awaiting input from Cloud Services

===GFX (milan)===

* Ongoing graphics driver/hardware related issues being looked at in the release (33) channel. This is having a negative impact on looking at the beta tracked issues.

* Second round of graphics planning. With input from desktop and date changes from Firefox OS, here is the updated list of priorities:

{| class="wikitable" width="100%"
! style="text-align: center;" width: "50%;" | Previous Plans !! style="text-align: center;" width: "50%;" | Current Plans
|-
|
* Firefox OS 2.0 & 2.1 blockers
* E10S support (OMTC)
* Firefox OS memory usage reduction
* Project Silk support
** Scrolling physics + v-sync
* APZ improvements
** OOP support
** fake overscroll
* WebGL desktop performance (critical items)
* WebGL mobile performance
------ Line for Gecko 39/2.2/GDC/MWC ------
* OMTC everywhere
* APZ on desktop
* Tiling on desktop
------ Line for Gecko 41 ------
* Skia canvas
* WebGL performance parity on desktop
------ Line for Gecko 43 ------
* Skia content
* Multi-threaded content painting
------ Line for Gecko 45 ------
------ Line for 2015 ------
|
* Firefox OS 2.0 & 2.1 blockers
* E10S support (OMTC)
* ↓ Firefox OS memory usage reduction (minimal)
* Project Silk support
** Scrolling physics + v-sync
------ Line for Gecko 38/2.2 ------
* WebGL2 support + demo
* WebGL desktop performance (critical items)
* (new) Desktop OOM driver related issues
------ Line for Gecko 39/GDC ------
* OMTC everywhere
* APZ on desktop
* Tiling on desktop
* (new) Desktop scrolling performance
------ Line for Gecko 41 ------
* ↓ APZ improvements
** OOP support
** fake overscroll
* ↓ WebGL mobile performance
* ↓ Skia canvas
* ↓ WebGL performance parity on desktop
------ Line for Gecko 44 ------
------ Line for 2015 ------
* ↓ Skia content
* ↓ Multi-threaded content painting
|
|}

===JS (naveed)===


{{readonly}}

* THIS WEEK
**Bug 1087468: We still have regressions we the inlining of any for-loop, still looking at the NavierStokes improvement, I was able to isolated a better patch which give us ~22.5% improvement on NavierStokes, without regressing other benchmarks.

* Compacting GC (bug 650161) Compacting shell tests are now enabled on inbound

* Only perform a minor GC when the store buffer is full (bug 1089582)

* Landed new memory organization for non-native objects (bug 1073842)




=== Emscripten (naveed)===
{{readonly}}

* Updated emscripten unit test system to run on nightly, aurora and beta [http://clb.demon.fi:8112/waterfall test results]
** Uncovered a number of regressions in the dev channels
*** These have all (or almost all) been filed. Let us know if you need any assistance replicating the issues

===Layout (jet/dbaron)===


{{readonly}}

* Platform-wide business planning last week and this week.
* Minor updates to Q4 [[Platform/2014-Q4-Goals#Layout|Layout goals]]

===Media (mreavy)===


{{readonly}}


* Found major perf issue on B2G caused by --- the network activity status anim! {{Bug|1091240}} and follow-ons.
** Caused 20-30% CPU use and multi-second network latency in some cases. Wallpaper fix is to reduce frame rate to 5-6FPS from 30fps (and the anim had ~5 duplicates of each frame anyways, so that doesn't even change the visual)
** Dramatically improves Hello on B2G; also helps with fetching larger amounts of content/PDFs/images.
* Fixed getUserMedia regression (delay) on Mac audio when switching outputs (like plugging in earbuds) due to bug 848954 on OSX 10.6-10.9
** Found that Yosemite (10.10) has broken this (and output panning to right speaker to avoid mic on top of left speaker)
* Progress towards using Promises with getUserMedia/CreateOffer/etc at TPAC last week


* Hope to land fix for 3 top WebRTC oranges today



===Necko (dougt/jduell)===




* B2G emulator perma-oranges: ran on desktop emulator and didn't see timeout, so we're blaming on hardware and disabling tests for now.
* fixed topcrasher (Avast HTTP scanning prevented shutdown) ({{bug|1087674}})
* Upgrading to v15 of the HTTP/2 spec.
* OpenVPN API is getting close. Unclear how soon we'll get UI/webAPI done ({{bug|1033580}})





===Performance (vladan)===








===Seceng (dougt)===








===Shumway (tschneidereit)===








===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

==<Read only beyond this point>==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2014-10-28

2014-10-28T18:16:09Z

Naveed: /* JS (naveed) */ our ask

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}
* 33.0.2 ships today - going out with updates enabled at 5% to collect data
* 34 beta4 desktop ships today
* 34 beta4 mobile ships tomorrow
;Next beta go to builds
* Desktop - Thu (beta5)
* Mobile - Mon (beta6)

===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)

* Tree Closing Window on Saturday, November 1. {{bug|1087431}} is the tracker.
** An unusually long window -- approx 11-1/2 hours.
** Most of the work is network related, with interruptions in traffic from time to time.
** We'll leave trees "open", but developers should expect longer than normal build times and potential need to restart some jobs.

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===
{{readonly}}
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 7.77] (last week: 4.41).
* Android 4.0 talos was hidden across all trees last week. Some suites had failure rates as high as 37%. {{bug|1088019}} tracks unhiding it.
** Overall Android 4.0 failure rates across all test suites is around 10%, not including jobs that get automatically retriggered by buildbot. {{bug|1059797}} (landed on fx-team today after ~6wks of inactivity) will hopefully help, otherwise more hiding will be forthcoming.
* Numerous test disablings this week due to inactivity. More likely to come as I get time to go through the list.
* 30 intermittent failures marked as fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2014-10-21&f1=cf_last_resolved&query_format=advanced&list_id=11461559 List] - Thanks!.
** Thanks to William Chen for fixing {{bug|1033464}}, a longstanding Shadow DOM leak.

===CritSmash (dbolter)===

===MemShrink (njn)===
* Valentin Gosu [https://bugzilla.mozilla.org/show_bug.cgi?id=1079705 fixed a significant memory regression involving resource timing] that was detected by [https://areweslimyet.com AWSY].
* Mike Hommey landed [https://bugzilla.mozilla.org/show_bug.cgi?id=1083686 logalloc], a tool for recording and replaying heap allocations. It will allow easier testing of different heap allocators, such as jemalloc3.

===Stability (kairo)===
* A lot of work still flowing into 33 release, atm mainly {{bug|1089413}} (GFX, should be fixed in 33.0.2) and {{bug|1087674}} (shutdown issues with OpenH264 updates being MITM-ed by Avast SSL scanning).
* Nightly and Aurora have some recent GFX issues to sort out.
* Nightly had a crash spike caused by the landing of {{bug|865314}} (SSL/SPDY-related), fixed by backout in today's Nightly.

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===








===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===




* Telemetry is now submitting with a user ID, so we can measure things by user and not just by session.
** Step towards unifying FHR and Telemetry.

===Developer Services (gps/lthomson)===






* gps: [http://gregoryszorc.com/blog/2014/10/27/implications-of-using-bugzilla-for-firefox-patch-development/ "Implications of Using Bugzilla for Firefox Patch Development"]



===Developer Tools (prouget)===








===DOM (jst/overholt)===







* still focused on getting Service Workers usable on [https://treeherder.mozilla.org/ui/#/jobs?repo=maple Maple]
* fixing IndexedDB quota prompt situation with plan to uplift to Aurora
* please file any fallout from WebSocket in Workers {{bug|504553}}

===Electrolysis (e10s) (blassey)===

* Please help dogfood e10s in Nightly!
** To opt-in, open "Preferences" and check the "Enable E10S (multi-process)" checkbox.
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect


* Enabling more e10s tests
* Watch for add-on breakage even with e10s disabled from {{bug|1030420}} ("Enable dom.compartment_per_addon by default on Nightly"). This change is intended to help find e10s add-on bugs, even when e10s is disabled.


* Big changes to e10s printing ({{bug|927188}}) and plugins ({{bug|641685}}, {{bug|669200}}, {{bug|1044182}}) coming soon
* e10s maybe be enabled by default for Nightly testing within the next couple weeks, so please your test features and favorite add-ons now!
** Add-ons that specifically marked as e10s-compatible in their manifests will be disabled ({{bug|1088309}}) on e10s first run, but brave testers can reenable them.



===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===
====Done since last week that might impact others====
* worked on Reader mode/reading list
====Doing this week that might impact others====
* continuing work on reader mode/reading list
====Working on that is dependent on others====
* minifying JS is waiting on platform team dependency

===GFX (milan)===








* Desktop requirements, new B2G timeline and requirements - GFX has a meeting with all interested parties tomorrow to sort out the priorities of the new requests.

===JS (naveed)===








Mozilla SpiderMonkey in the news:
* [http://arewefastyet.com/ SpiderMonkey is faster than V8 on Octane]
** [http://arewefastyet.com/#machine=17 With VisualStudio 2013 PGO we are neck and neck even on Windows]
* [http://robert.ocallahan.org/2014/10/are-we-fast-yet-yes-we-are.html Roc's blog about SpiderMonkey on Octane]
**[https://news.ycombinator.com/item?id=8518903 hacker news]
**[http://www.reddit.com/r/programming/comments/2kk2us/spidermonkey_has_passed_v8_on_octane_performance/ reddit]

* Compiler (JIT)
** {{bug|1087232}}: Don't atomize eval strings for the eval cache
** {{bug|1087963}}: Fixed Array.prototype.slice to not be horribly slow on sparse arrays, issue reported by the Google Inbox people.

* Garbage Collection
** {{bug|650161}} : Worked on compacting GC - Try to get CGC tests enabled on tbpl

* Front End and Other
** Shared object heap POC: working (locks, conditions, queues, arrays, structures); nice speedup on mbrot, raytrace though challenges remain
** {{bug|1088709}}: Implement SIMD loads/stores in the interpreter.

* What will your team do this week that might impact others?
** Investigating JSBench and BrowserMark 2.1 performance. We may need some help from other teams (DOM Network) to help figure out performance bottlenecks. Let me know who the right person(s) would be.

===Layout (jet/dbaron)===


{{readonly}}
* W3C TPAC (CSS & SVG working groups) meeting face-to-face this week. Spec changes coming up!

===Media (mreavy)===


{{readonly}}


* Continuing to dog down WebRTC issues in 2.1
** Improved getUserMedia framerate (regression due to bug 848954 (MediaStreamGraph rework)
* Hello (loop) is now fully un-throttled in Beta; everyone should see it in their customization panel
* Only small updates to Beta since last week for Hello, stable
* working to resolve Mac audio regressions from bug 848954 when switching audio outputs



===Necko (dougt/jduell)===


{{readonly}}



* Alas, we had to back out enforcing HTTP framing (i.e. requiring content-length header to match actual length). Broke too many websites. This means the download manager will once again not warn about incomplete downloads. We have some plans for a more targeted set of fixes. ({{bug|1088850}})




===Performance (vladan)===








===Seceng (dougt)===








===Shumway (tschneidereit)===








===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

* Portland All-Hands
** (Milan) Would like to have a session in Portland on alternatives to crash reports to get us back "bad failures". For example, we detect a bad driver, which leads to a the sub-optimal experience for the user. We fall back to non-accelerated setup, and warn the user about it, also letting them send us the information similar to what crash report would send. We'd need a lot of different teams represented - who should come, who should run with this?
** [https://wiki.mozilla.org/Portland_coincidental_work_week#Time_Blocks_.28subject_to_change.29 Portland All-Hands free time blocks] wiki to advertise BoF sessions.

==<Read only beyond this point>==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2014-10-28

2014-10-28T17:23:55Z

Naveed: /* JS (naveed) */ more update

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lsblakk/sylvestre/lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}

===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)

* Tree Closing Window on Saturday, November 1. {{bug|1087431}} is the tracker.
** An unusually long window -- approx 11-1/2 hours.
** Most of the work is network related, with interruptions in traffic from time to time.
** We'll leave trees "open", but developers should expect longer than normal build times and potential need to restart some jobs.

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===

===CritSmash (dbolter)===

===MemShrink (njn)===
* Valentin Gosu [https://bugzilla.mozilla.org/show_bug.cgi?id=1079705 fixed a significant memory regression involving resource timing] that was detected by [https://areweslimyet.com AWSY].
* Mike Hommey landed [https://bugzilla.mozilla.org/show_bug.cgi?id=1083686 logalloc], a tool for recording and replaying heap allocations. It will allow easier testing of different heap allocators, such as jemalloc3.

===Stability (kairo)===

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===








===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===







* still focused on getting Service Workers usable on [https://treeherder.mozilla.org/ui/#/jobs?repo=maple Maple]
* fixing IndexedDB quota prompt situation with plan to uplift to Aurora

===Electrolysis (e10s) (blassey)===

* Please help dogfood e10s in Nightly!
** To opt-in, open "Preferences" and check the "Enable E10S (multi-process)" checkbox.
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect


* Enabling more e10s tests
* Watch for add-on breakage even with e10s disabled from {{bug|1030420}} ("Enable dom.compartment_per_addon by default on Nightly"). This change is intended to help find e10s add-on bugs, even when e10s is disabled.


* Big changes to e10s printing ({{bug|927188}}) and plugins ({{bug|641685}}, {{bug|669200}}, {{bug|1044182}}) coming soon
* e10s maybe be enabled by default for Nightly testing within the next couple weeks, so please your test features and favorite add-ons now!
** Add-ons that specifically marked as e10s-compatible in their manifests will be disabled ({{bug|1088309}}) on e10s first run, but brave testers can reenable them.



===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===








===GFX (milan)===








===JS (naveed)===








Mozilla SpiderMonkey in the news:
* [http://arewefastyet.com/ SpiderMonkey is faster than V8 on Octane]
** [http://arewefastyet.com/#machine=17 With VisualStudio 2013 PGO we are neck and neck even on Windows]
* [http://robert.ocallahan.org/2014/10/are-we-fast-yet-yes-we-are.html Roc's blog about SpiderMonkey on Octane]
**[https://news.ycombinator.com/item?id=8518903 hacker news]
**[http://www.reddit.com/r/programming/comments/2kk2us/spidermonkey_has_passed_v8_on_octane_performance/ reddit]

* Compiler (JIT)
** {{bug|1087232}}: Don't atomize eval strings for the eval cache
** {{bug|1087963}}: Fixed Array.prototype.slice to not be horribly slow on sparse arrays, issue reported by the Google Inbox people.

* Garbage Collection
** {{bug|650161}} : Worked on compacting GC - Try to get CGC tests enabled on tbpl

* Front End and Other
** Shared object heap POC: working (locks, conditions, queues, arrays, structures); nice speedup on mbrot, raytrace though challenges remain
** {{bug|1088709}}: Implement SIMD loads/stores in the interpreter.

===Layout (jet/dbaron)===








===Media (mreavy)===








===Necko (dougt/jduell)===








===Performance (vladan)===








===Seceng (dougt)===








===Shumway (tschneidereit)===








===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

* Portland All-Hands
** (Milan) Would like to have a session in Portland on alternatives to crash reports to get us back "bad failures". For example, we detect a bad driver, which leads to a the sub-optimal experience for the user. We fall back to non-accelerated setup, and warn the user about it, also letting them send us the information similar to what crash report would send. We'd need a lot of different teams represented - who should come, who should run with this?
** [https://wiki.mozilla.org/Portland_coincidental_work_week#Time_Blocks_.28subject_to_change.29 Portland All-Hands free time blocks] wiki to advertise BoF sessions.

==<Read only beyond this point>==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2014-10-28

2014-10-28T17:23:21Z

Naveed: /* JS (naveed) */ update

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lsblakk/sylvestre/lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}

===Build Changes (gps)===
(Build changes of which engineers should be aware.)








===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)








===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)

* Tree Closing Window on Saturday, November 1. {{bug|1087431}} is the tracker.
** An unusually long window -- approx 11-1/2 hours.
** Most of the work is network related, with interruptions in traffic from time to time.
** We'll leave trees "open", but developers should expect longer than normal build times and potential need to restart some jobs.

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===

===CritSmash (dbolter)===

===MemShrink (njn)===
* Valentin Gosu [https://bugzilla.mozilla.org/show_bug.cgi?id=1079705 fixed a significant memory regression involving resource timing] that was detected by [https://areweslimyet.com AWSY].
* Mike Hommey landed [https://bugzilla.mozilla.org/show_bug.cgi?id=1083686 logalloc], a tool for recording and replaying heap allocations. It will allow easier testing of different heap allocators, such as jemalloc3.

===Stability (kairo)===

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===








===Accessibility (dbolter)===








===B2G Services (dougt)===








===Cloud Services (mmayo)===








===Desktop Platform (bsmedberg)===








===Developer Tools (prouget)===








===DOM (jst/overholt)===







* still focused on getting Service Workers usable on [https://treeherder.mozilla.org/ui/#/jobs?repo=maple Maple]
* fixing IndexedDB quota prompt situation with plan to uplift to Aurora

===Electrolysis (e10s) (blassey)===

* Please help dogfood e10s in Nightly!
** To opt-in, open "Preferences" and check the "Enable E10S (multi-process)" checkbox.
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect


* Enabling more e10s tests
* Watch for add-on breakage even with e10s disabled from {{bug|1030420}} ("Enable dom.compartment_per_addon by default on Nightly"). This change is intended to help find e10s add-on bugs, even when e10s is disabled.


* Big changes to e10s printing ({{bug|927188}}) and plugins ({{bug|641685}}, {{bug|669200}}, {{bug|1044182}}) coming soon
* e10s maybe be enabled by default for Nightly testing within the next couple weeks, so please your test features and favorite add-ons now!
** Add-ons that specifically marked as e10s-compatible in their manifests will be disabled ({{bug|1088309}}) on e10s first run, but brave testers can reenable them.



===Firefox Desktop (gavin)===








===Firefox Mobile (snorp/blassey/mfinkle)===








===GFX (milan)===








===JS (naveed)===








Mozilla SpiderMonkey in the news:
[http://arewefastyet.com/ SpiderMonkey is faster than V8 on Octane]
[http://arewefastyet.com/#machine=17 With VisualStudio 2013 PGO we are neck and neck even on Windows]
[http://robert.ocallahan.org/2014/10/are-we-fast-yet-yes-we-are.html Roc's blog about SpiderMonkey on Octane]
[https://news.ycombinator.com/item?id=8518903 hacker news]
[http://www.reddit.com/r/programming/comments/2kk2us/spidermonkey_has_passed_v8_on_octane_performance/ reddit]

* Compiler (JIT)
** {{bug|1087232}}: Don't atomize eval strings for the eval cache
** {{bug|1087963}}: Fixed Array.prototype.slice to not be horribly slow on sparse arrays, issue reported by the Google Inbox people.

* Garbage Collection
** {{bug|650161}} : Worked on compacting GC - Try to get CGC tests enabled on tbpl

* Front End and Other
** Shared object heap POC: working (locks, conditions, queues, arrays, structures); nice speedup on mbrot, raytrace though challenges remain
** {{bug|1088709}}: Implement SIMD loads/stores in the interpreter.

===Layout (jet/dbaron)===








===Media (mreavy)===








===Necko (dougt/jduell)===








===Performance (vladan)===








===Seceng (dougt)===








===Shumway (tschneidereit)===








===WebAPI (overholt)===








==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

* Portland All-Hands
** (Milan) Would like to have a session in Portland on alternatives to crash reports to get us back "bad failures". For example, we detect a bad driver, which leads to a the sub-optimal experience for the user. We fall back to non-accelerated setup, and warn the user about it, also letting them send us the information similar to what crash report would send. We'd need a lot of different teams represented - who should come, who should run with this?
** [https://wiki.mozilla.org/Portland_coincidental_work_week#Time_Blocks_.28subject_to_change.29 Portland All-Hands free time blocks] wiki to advertise BoF sessions.

==<Read only beyond this point>==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2014-10-14

2014-10-14T19:00:10Z

Naveed: /* JS (naveed) */

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|-
|}

* It's release day! Firefox 33 released today! Congratulations!

...and the trains keep on rolling
* beta = 34
* aurora = 35
* nightly = 36

* Firefox 34 beta1 is scheduled to release this Thursday
* Aurora updates are scheduled to be re-enabled on Friday

* Review: Firefox 34 beta release notes
** Desktop https://www-dev.allizom.org/en-US/firefox/34.0beta/releasenotes/
** Mobile https://www-dev.allizom.org/en-US/mobile/34.0beta/releasenotes/

===Build Changes (gps)===
(Build changes of which engineers should be aware.)



===RelEng (catlee)===
(Repo, test, and other information for engineers from the release engineering team.)



===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===
{{readonly}}
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 4.15] (last week: 4.51).
* {{bug|906716}} - Intermittent B2G emulator "timed out after 1000 seconds of no output" remains #1 by a wide margin.
* All Marionette tests are now hidden on the B2G emulator for an ongoing extremely high failure rate. Unhiding is tracked in {{bug|1081529}}.
* 22 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C &resolution=FIXED&o1=greaterthan&v1=2014-10-07&f1=cf_last_resolved&query_format=advanced&list_id=11367820 List] - Thanks!.

===CritSmash (dbolter)===
* small uptick in risk factor.
* please remember to factor in security fix time for Q4 and 2015 planning.

===MemShrink (njn)===
* Jan de Mooij [https://bugzilla.mozilla.org/show_bug.cgi?id=1073700 optimized the JS engine's shape representation], which gave a 7 MiB win on JS memory usage on [https://areweslimyet.com/ AWSY].

===Stability (kairo)===

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*Team (jgriffin)===



===Accessibility (dbolter)===



===B2G Services (dougt)===



===Cloud Services (mmayo)===



===Desktop Platform (bsmedberg)===

* Mac V2 signing done and uplifted to 34 (will be in 34b1). Please keep your eyes peeled for possible regressions.
* As of this morning, MSVC2013 is now used for both win32 and win64 nightlies.
* We plan on folding gkmedias and mozjs back into xul.dll in the near future, and un-export JS symbols

===Developer Tools (prouget)===



===DOM (jst/overholt)===



===Electrolysis (e10s) (blassey)===


* Please help dogfood e10s in Nightly!
** To opt-in, open the "Preferences" and check the "Enable E10S (multi-process)" checkbox
** (same as flipping the "browser.tabs.remote.autostart" pref to true and restart Nightly.
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect
* {{bug|1076314}} - Ask Nightly users to dogfood e10s again!
** Less crashing!
** Improved add-on compatibility and DevTools
** PDF.js, Web Console, Spellchecking, WebRTC now work
* {{bug|875867}} - Fixed Safe Browsing for e10s
* {{bug|1067576}} - Fixed Web Console for e10s
* {{bug|942707}} - Fixed pdf.js for e10s

===Firefox Desktop (gavin)===



New iteration (36.1) starts today. Priorities are:

Engineering
* e10s
* Hello
* Forget button followup
* Yosemite - finishing what we can in the front-end
* Places performance
* Autocomplete: plan for shipping unified complete

UX
* Hello collaboration and screensharing
* Search improvements
* Forget button followup

===Firefox Mobile (snorp/blassey/mfinkle)===


====Work In Progress====
*Progress on MediaCodec patches
*Investigation into standalone WebRTC
*Privacy Coach
*Toolbar Refresh ({{bug|1071267}} {{bug|1019127}} {{bug|960746}} {{bug|1072464}} {{bug|1075531}})
*Second Screen ({{bug|1054959}} {{bug|1074567}})
You can find more on upcoming feature plans in the[[https://wiki.mozilla.org/Mobile/Roadmap| roadmap]]
====Landings from the past week====
===== Nightly ({{CENTRAL_VERSION}})=====
*Bottom divider is lost in Reading List ([https://bugzilla.mozilla.org/show_bug.cgi?id=919748 Bug 919748 ])
*Disable downloads and extension installs in guest mode ([https://bugzilla.mozilla.org/show_bug.cgi?id=1046941 Bug 1046941 ])
*Clearing private data on exit: "Always clear when quitting" often cropped/truncated in localizations, provide more space ([https://bugzilla.mozilla.org/show_bug.cgi?id=1048433 Bug 1048433 ])
*crash in java.lang.IllegalStateException: No current media session at com.google.android.gms.internal.gp.dV(Unknown Source) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1055764 Bug 1055764 ])
*Launching Firefox for the first time through an external intent should not display First Run experience ([https://bugzilla.mozilla.org/show_bug.cgi?id=1059792 Bug 1059792 ])
*crash in java.lang.NullPointerException: at org.mozilla.gecko.ChromeCast$2.onConnected(ChromeCast.java) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1061032 Bug 1061032 ])
*Performing searches with Wikipedia search engine immediately launches Fennec ([https://bugzilla.mozilla.org/show_bug.cgi?id=1063193 Bug 1063193 ])
*Feature other recommended add-ons in "Firefox Privacy Coach" add-on ([https://bugzilla.mozilla.org/show_bug.cgi?id=1064926 Bug 1064926 ])
*Warn user if a search query or isn't going over https ([https://bugzilla.mozilla.org/show_bug.cgi?id=1064998 Bug 1064998 ])
*HTML5 video playback is not paused in the browser after opening in external player (open with app) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1071831 Bug 1071831 ])
*'Set image as' option does not work when /mnt/sdcard/DCIM is missing ([https://bugzilla.mozilla.org/show_bug.cgi?id=1072978 Bug 1072978 ])
*Error bulk-inserting default favicons - android.database.sqlite.SQLiteConstraintException: PRIMARY KEY must be unique (code 19) @ android.database.sqlite.SQLiteConnection.nativeExecuteForLastInsertedRowId(Native Method) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1074340 Bug 1074340 ])
*Guest Mode notification persists on browser close ([https://bugzilla.mozilla.org/show_bug.cgi?id=1074343 Bug 1074343 ])
*Disable import from Android in Guest mode ([https://bugzilla.mozilla.org/show_bug.cgi?id=1074496 Bug 1074496 ])
*Error message for blocked downloads is wrong ([https://bugzilla.mozilla.org/show_bug.cgi?id=1074505 Bug 1074505 ])
*Tinted status bar visible during full-screen video ([https://bugzilla.mozilla.org/show_bug.cgi?id=1074924 Bug 1074924 ])
*Tapping on URL bar does not dismiss the tabs tray ([https://bugzilla.mozilla.org/show_bug.cgi?id=1076692 Bug 1076692 ])
*crash in java.lang.NullPointerException: at org.mozilla.search.SearchWidget.addView(SearchWidget.java) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1078182 Bug 1078182 ])
*Android builds are going to burn when Gecko 35 merges to Beta ([https://bugzilla.mozilla.org/show_bug.cgi?id=1079629 Bug 1079629 ])
*crash in java.lang.RuntimeException: Parcel android.os.Parcel@<addr>: Unmarshalling unknown type code 4522062 at offset 736 at android.os.Parcel.readValue(Parcel.java) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1079876 Bug 1079876 ])
*Let search activity ride the trains ([https://bugzilla.mozilla.org/show_bug.cgi?id=1081249 Bug 1081249 ])
*crash in java.lang.NullPointerException: key == null at java.util.EnumMap.putImpl(EnumMap.java) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1081948 Bug 1081948 ])

===GFX (milan)===



===JS (naveed)===

{{readonly}}
* [https://wiki.mozilla.org/Platform/2014-Q4-Goals#JS Q4 Goals]

===Layout (jet/dbaron)===

{{readonly}}
* [https://wiki.mozilla.org/Platform/2014-Q4-Goals#Layout Q4 Goals Posted!]

===Media (jesup)===


* [https://wiki.mozilla.org/Platform/2014-Q4-Goals#Media Media Playback Q4 Goals Posted!]
* Loop is in Beta now!
** We've implemented throttling of visibility as this is a "beta" feature with a soft rollout for 34
*** This means that in Beta the Loop icon will be in the "Customize" menu, AND due to throttling you may not see it there initially unless you set "loop.throttled = false" in about:config
* Forwarding of video to PeerConnection is about to land in Nightly and will likely uplift to Aurora (most is there already).

===Necko (dougt/jduell)===



* Network-changed events for Linux/B2G has landed on inbound ({{bug|1008091}}): helps with lame-network wedges.
* Landed "set network offline on a per app basis" ({{bug|786419}})
* Opportunistic Encryption (OE) for HTTP/2 (i.e. if server opts-in we'll upgrade http to use TLS w/o certs) has landed ({{bug|1003448}}). Akamai will be our first main use case.
* Almost done mopping up cache2 fallout bugs ({{bug|1074832}})
* Looks like we can reduce memory usage and technical debt by merging parts of imglib cache with cache2 (honza, :seth)
* Resource timing has stuck in the tree, but e10s support bounced ({{bug|1064706}})
* We'll be participating next year in an EU-funded academic/industry research project (NEAT) to explore ways to improve application protocols (something better than TCP) practically on the internet.

===Performance (vladan)===



===Seceng (dougt)===



===Shumway (tschneidereit)===



===WebAPI (overholt)===



==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)
* cpeterson seeking feedback on this weekly meeting:
** Is this meeting still useful?
** What value do you get (or want to get) from attending the meeting compared to just reading the wiki notes?
** What value do you get from the wiki notes compared to team's sharing their updates on relevant mailing lists?

==<Read only beyond this point>==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
11:04 dholbert: cpeterson, I suspect more folks are watching on AirMo [I am, at least :)]
11:04 cpeterson: dholbert: what's on AirMo now?
11:04 jesup: Platform meeting does force people to actually *write* those notes....
11:04 dholbert: cpeterson, the eng meeting
11:06 cpeterson: jesup: *if* they update the wiki notes :)
11:06 cpeterson: dholbert: which eng meeting?
11:07 dholbert: cpeterson, lol :) the one right now, I think. snorp just finished talking about roku stuff
11:08 cpeterson: dholbert: oh yeah..
11:10 jesup: lmandel: mreavy we will ramp up over a week or two depending on how the servers look, and how usage looks
11:11 lmandel: jesup: Thanks. Found about about this from pjarret. This was a surprise for me and for QE.
11:12 jesup: IIRC product (and maybe services) wanted that, though I wasn't directly involved. Services may have been concerned about getting swamped all at once.
11:14 lmandel: jesup: Yup. I just didn't realize we were doing this on beta. I thought it was only release.
11:16 cpeterson: lmandel: fyi, tracking protection is still broken with e10s: bug 1055186
</pre>

Platform/2014-Q4-Goals

2014-10-07T19:58:58Z

Naveed: /* JS */

Platform/2014-Q4-Goals

2014-10-07T19:57:53Z

Naveed: /* JS */

Platform/2014-Q4-Goals

2014-10-07T19:57:36Z

Naveed: /* JS */

2014-08-12T18:04:42Z

Naveed: /* JS (naveed) */

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lsblakk/sylvestre)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|}

* beta6 desktop goes live today
* beta6 mobile goes live tomorrow
* 3 more weeks until Firefox 32 release (Sep 2)
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&o14=notequals&f13=OP&j16=OR&o34=equals&j11=OR&f29=CP&v5=wontfix&f12=CP&f14=cf_status_firefox32&o17=notequals&o20=notequals&f21=CP&known_name=Tracking32%2B-Remaining&f10=OP&f19=OP&f31=CP&f1=OP&f20=cf_status_firefox32&j13=OR&f8=cf_status_firefox32&f0=OP&f33=CP&j19=OR&v34=%2B&f34=cf_tracking_firefox32&f18=CP&query_based_on=Tracking32%2B-Remaining&query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f5=cf_status_firefox32&f17=cf_status_firefox32&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP&list_id=10986719 tracking ~40 bugs] for Beta
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&list_id=10986737&o14=notequals&f13=OP&j16=OR&o34=equals&f29=CP&v5=wontfix&f12=CP&f14=cf_status_firefox33&o17=notequals&o20=notequals&f21=CP&known_name=Tracking32%2B-Remaining&f10=OP&f19=OP&f1=OP&f31=CP&f20=cf_status_firefox32&f0=OP&f8=cf_status_firefox33&j13=OR&f33=CP&v34=%2B&j19=OR&f34=cf_tracking_firefox33&f18=CP&query_based_on=Tracking32%2B-Remaining&query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f5=cf_status_firefox33&f17=cf_status_firefox32&v8=fixed&f6=CP&v14=verified&f7=OP&o8=notequals&f16=OP tracking ~50 bugs] for Aurora

===Build Changes (gps)===
(Build changes of which engineers should be aware.)



===RelEng (bhearsum)===
(Repo, test, and other information for engineers from the release engineering team.)


* [https://groups.google.com/forum/#!topic/mozilla.dev.platform/RGHGZuvQn24 Upcoming changes to Mac package layout, signing]

===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===
{{readonly}}
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ N/A] (still investigating {{bug|1046162}}) (Previous Week: N/A).
* 21 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2014-08-05&f1=cf_last_resolved&query_format=advanced&list_id=10986873 List] - Thanks!.
** Thanks to Martijn Wargers for fixing up many longstanding test issues that came to light with recent logging changes.

===CritSmash (dbolter)===

===MemShrink (njn)===
* Kyle Huey got [https://bugzilla.mozilla.org/show_bug.cgi?id=1038943 leak detection of B2G mochitests] turned on, after fixing numerous leaks that it detected along the way.
* Thanks to Pin and Jocelyn for jumping on some of the reported leaks.
* This is not exactly MemShrink, but Eric Rahm [https://bugzilla.mozilla.org/show_bug.cgi?id=1027921 improved the deadlock detector] so it runs much faster and uses vastly less memory, which makes debug builds less painful to use.

===Stability (kairo/bsmedberg)===
* Beta crash rate is high due to an adware-related crash that got worsened by trying to fix it (see {{bug|1038243}}). Cause seems to be a forgotten bump of IIDs which will be done in {{bug|1051858}}.

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*team (jgriffin)===



===App Tools (prouget)===



===B2G Services (dougt)===



===Cloud Services (mmayo)===



===Developer Tools (robcee)===



===DOM (jst/overholt)===



===Electrolysis (e10s) (blassey)===



===Firefox Desktop (gavin)===


====Summary of Work In Progress====
* You can find the most recently completed iteration performance report [https://wiki.mozilla.org/Firefox/IterativeDevelopment/IT-34.1PerformanceReport here]
* You can see the status of the current iteration in progress [https://docs.google.com/a/mozilla.com/spreadsheets/d/10sr6YhDNmO4oimlNtxDZ5fe6IaQKmZ7gqT-ZWqAygrI/edit#gid=1914765814 here]
====Summary of Recent Landings====
* Team landed 26 bugs over the last week, for the first half of the 34.2 iteration.
* Details of landings from the past week can be seen [https://bugzilla.mozilla.org/buglist.cgi?f1=flagtypes.name&list_id=10986223&o1=substring&resolution=FIXED&o2=substring&chfieldto=Now&chfield=resolution&query_format=advanced&chfieldfrom=2014-08-05&f2=flagtypes.name&chfieldvalue=FIXED&v1=firefox-backlog&v2=%2B here]

===Firefox Mobile (snorp/blassey/mfinkle)===


====Work In Progress====
*Search activity: Enabled in Nightly! Try it out. See [http://blog.margaretleibovic.com/post/93528710518/firefox-for-android-search-experiments blog post] for some details.
*Tablet refresh: Continuing progress on the tab strip implementation ([https://dl.dropboxusercontent.com/u/1187037/new-tablet.png screenshot]).
** {{bug|1046200}} - Create BrowserApp.isNewTablet()
** {{bug|1047561}} - Create settings UI for enabling the new tablet UI
** {{bug|1048575}} - Disable dynamic toolbar when in new tablet UI
*Janus https://wiki.mozilla.org/Mobile/Janus
**Janus Proxy - Cache improvements
**UI improvements/fixes to addon
You can find more on upcoming feature plans in the[[https://wiki.mozilla.org/Mobile/Roadmap| roadmap]]
===== Nightly ({{CENTRAL_VERSION}})=====
*Allow users to "try again" more than once on new error pages. ([https://bugzilla.mozilla.org/show_bug.cgi?id=910893 Bug 910893 ])
*YouTube HTML5 player does not offer full-screen toggle for embedded YouTube video for Firefox for Android ([https://bugzilla.mozilla.org/show_bug.cgi?id=947841 Bug 947841 ])
*When backspacing the last character of the current page in Firefox for Android's URL bar, it frequently reappears (highlighted, due to autosuggest) and needs to be backspaced again ([https://bugzilla.mozilla.org/show_bug.cgi?id=984057 Bug 984057 ])
*Pasting into url bar does not bring up search screen ([https://bugzilla.mozilla.org/show_bug.cgi?id=1039766 Bug 1039766 ])
*Up scaled and low resolution icons on bookmarks panel, history panel and recent tabs panel ([https://bugzilla.mozilla.org/show_bug.cgi?id=1046579 Bug 1046579 ])
*crash in java.lang.IllegalArgumentException: Property does not exist at org.mozilla.gecko.util.NativeJSObject.getString(Native Method) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1046880 Bug 1046880 ])
*Add ability to stop mirroring a tab ([https://bugzilla.mozilla.org/show_bug.cgi?id=1046971 Bug 1046971 ])
*Take advantage of nsIURIFixup improvements for faster location bar searches ([https://bugzilla.mozilla.org/show_bug.cgi?id=1047607 Bug 1047607 ])
*Only reset search activity when launched from new intent ([https://bugzilla.mozilla.org/show_bug.cgi?id=1048022 Bug 1048022 ])
*Make all empty view images 90x90dp ([https://bugzilla.mozilla.org/show_bug.cgi?id=1048941 Bug 1048941 ])
*Searching for something in search activity it will open a new about:blank page in stead of search results ([https://bugzilla.mozilla.org/show_bug.cgi?id=1049650 Bug 1049650 ])

===Firefox OS Communications (scravag)===



===Firefox OS Connectivity (vchang)===



===Firefox OS Devices/Porting (ericchou)===
{{readonly}}
* Gonk team (led by Thomas Tsai)
** On-site support: Kai-Zen Li @ India (7/28 ~ 8/8)
** [http://goo.gl/fQbpcA Tarako]: Solving gating issues which were reported by Spice/Intex
** [http://goo.gl/fQbpcA Dolphin]: SPRD PTR2 and perf issues
** [http://goo.gl/e015f0 Woodduck]: github code sync and function ready lists
** [http://goo.gl/tHXAE9 Flame]: KK + v1.4/v2.0 porting

* Bluetooth (members: Shawn Huang, Ben Tian, Jamin Liu, Jocelyn Liu)
** {{Bug|1045486}}, {{Bug|1048093}} - Bluetooth transferring doesn't work either when bluetooth backend is BlueZ or Bluedroid - both landed
** {{Bug|1005934}} - Move bluedroid to a separate process (target 2.2)
*** Thomas Zimmermann worked on it and Ben and Shawn are responsible for reviewing.
** The whole team met with Google Chrome OS bt team to discuss about WebBluetooth API.
** Moz's Bluetooth Low Energy API draft - https://workflowy.com/shared/91b7d347-039f-9960-04f9-f1711ad02281/ (WIP)

* Media Playback (members: Bruce Sun, Blake Wu, Star Cheng)
** {{Bug|941302}} - PlatformDecoderModule for Firefox OS - landed (2.1 feat+)
** {{Bug|1009410}} - Expose graphic buffer to MediaCodec - waiting for CAF's response (2.1 feat+)
** {{Bug|1033902}} - Integrate AudioOffloadPlayer with MediaCodecReader and MediaCodecDecoder - reviewing (2.1 feat+)
** {{Bug|1033337}} - [dolphin] It took about 1.8-2.2s for music to start play (It was 1.4+, now 1.4-)
** {{Bug|1049325}} - Last frame is dropped with PlatformDecoderModule enabled - WIP (2.1 feat+)

* Device Storage & Stability (members: Alphan Chen)
** {{Bug|1043264}} - [MTP] Find out the needed MTP API (2.1 feat+)
** {{Bug|1050720}} - "storage-state-change" event will be triggered twice (should be 2.1 feat+)

===Firefox OS Media (slee)===
{{readonly}}
* ImageCaputre API implementation
** WIP
* Support recording media stream from OfflineAudioContext
** WIP
* Intermittent media test cases fixing
** in progress
* [blocker]Video playback doesn't start and buffering icon is seen forever
** analyzing
* async codec threading part
** reviewing

===Firefox OS Media Apps (hema)===



===Firefox OS Media Recording(pchang)===



===Firefox OS Performance (mlee)===



===Firefox OS Productivity (doliver)===



===Firefox OS RIL (htsai)===

{{readonly}}
#https://wiki.mozilla.org/TPE_RIL_team/2014-08-12

===Firefox OS Systems - Front End (gwagner)===



===Firefox OS Systems - Platform (timdream)===



===GFX (milan)===



===JS (naveed)===
{{readonly}}

* Intern Work Completed
** Implemented ES6 template strings - bug 1021368, bug 1024748, bug 1031397, bug 1034314, bug 1038259, bug 1038498
** Implemented ES6 String.raw and ToLength (self-hosted) - bug 1039774 and bug 1040196
** Implemented ES6 computed property names - bug 924688

* Compiler (JIT)
** {{bug|1039458}}: landed basic loop unrolling
** {{bug|1042833}}: removed JS_ION entirely

* Garbage Collection
** {{bug|650161}}: Compacting GC
*** currently it supports moving JSObjects only
*** most tests pass now but there are still some bugs to iron out
*** posted initial set of patches for review

* Front End and Other
** SharedArrayBuffer: cleaned up lock/futex POC code and spec somewhat
** {{bug|1047220}}: Shrink the static atoms table

===Layout (jet/dbaron)===

{{readonly}}
Some bugs of note:
*{{bug|996796}} Lots of style infrastructure for better animations and transitions
*{{bug|1018278}} Blacklist some Intel graphics drivers
*{{bug|927892}} Working on HTML5 Canvas filters

===Media (mreavy)===

{{readonly}}
* Windowsharing now refreshes the window list on each request - {{bug|1041369}} - thanks to new contributor Roman Skalish
** On windows, it offers to share some uninteresting windows at times, like the sharing indicator or the Windows menu
* GMP OpenH264 Mode 0 supported - {{bug|1051566}} - thanks to new contributor Mo Zanaty for providing fixes for the underlying webrtc.org code
* Windows OpenH264 IPC crash resolved ({{bug|1044245}})
* Aurora/33 updated with all important Screensharing and OpenH264 fixes

===Necko (dougt/jduell)===

{{readonly}}

* HTTP/2 on nightly wouldn't work with Twitter for a little while--mostly their fault.
* {{bug|1007020}} - XHR Progress Events need a way to read how many compressed bytes have been downloaded
* Getting closer to landing Resource Timing API
** {{bug|1047848}} - PerformanceResourceTiming objects can't be JSON.stringify'd
* Making progress on captive portal detection.

===Performance (vladan)===



===Seceng (keeler)===



{{Bug|1036546}} landed: soft-disable proprietary window.crypto functions/properties before removing them entirely (things like window.crypto.generateCRMFRequest now don't exist unless the pref "dom.unsafe_legacy_crypto.enabled" is true). See also {{Bug|1030963}}.

===Shumway (tschneidereit)===



===WebAPI (overholt)===



==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

==<Read only beyond this point>==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>

Platform/2014-08-12

2014-08-12T18:04:15Z

Naveed: /* JS (naveed) */

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Engineering Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0800">Pacific Standard Time</abbr>
{{conf|98411}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / [https://air.mozilla.org/ Air Mozilla] / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Need To Know==
(Release and system issues that may impact engineering this week.)

===Notices/Schedule (lsblakk/sylvestre)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''
|-
!colspan="4" style="color:black;"|Trains
|-
|Central: {{CENTRAL_VERSION}}
|Aurora: {{AURORA_VERSION}}
|Beta: {{BETA_VERSION}}
|Release: {{RELEASE_VERSION}}
|}

* beta6 desktop goes live today
* beta6 mobile goes live tomorrow
* 3 more weeks until Firefox 32 release (Sep 2)
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&o14=notequals&f13=OP&j16=OR&o34=equals&j11=OR&f29=CP&v5=wontfix&f12=CP&f14=cf_status_firefox32&o17=notequals&o20=notequals&f21=CP&known_name=Tracking32%2B-Remaining&f10=OP&f19=OP&f31=CP&f1=OP&f20=cf_status_firefox32&j13=OR&f8=cf_status_firefox32&f0=OP&f33=CP&j19=OR&v34=%2B&f34=cf_tracking_firefox32&f18=CP&query_based_on=Tracking32%2B-Remaining&query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f5=cf_status_firefox32&f17=cf_status_firefox32&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP&list_id=10986719 tracking ~40 bugs] for Beta
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&list_id=10986737&o14=notequals&f13=OP&j16=OR&o34=equals&f29=CP&v5=wontfix&f12=CP&f14=cf_status_firefox33&o17=notequals&o20=notequals&f21=CP&known_name=Tracking32%2B-Remaining&f10=OP&f19=OP&f1=OP&f31=CP&f20=cf_status_firefox32&f0=OP&f8=cf_status_firefox33&j13=OR&f33=CP&v34=%2B&j19=OR&f34=cf_tracking_firefox33&f18=CP&query_based_on=Tracking32%2B-Remaining&query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f5=cf_status_firefox33&f17=cf_status_firefox32&v8=fixed&f6=CP&v14=verified&f7=OP&o8=notequals&f16=OP tracking ~50 bugs] for Aurora

===Build Changes (gps)===
(Build changes of which engineers should be aware.)



===RelEng (bhearsum)===
(Repo, test, and other information for engineers from the release engineering team.)


* [https://groups.google.com/forum/#!topic/mozilla.dev.platform/RGHGZuvQn24 Upcoming changes to Mac package layout, signing]

===Upcoming Outages/Upgrades===
(System outages/upgrades and tree closures that impact engineering.)

==Quality Programs==
(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

===OrangeFactor (ryanvm)===
{{readonly}}
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ N/A] (still investigating {{bug|1046162}}) (Previous Week: N/A).
* 21 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2014-08-05&f1=cf_last_resolved&query_format=advanced&list_id=10986873 List] - Thanks!.
** Thanks to Martijn Wargers for fixing up many longstanding test issues that came to light with recent logging changes.

===CritSmash (dbolter)===

===MemShrink (njn)===
* Kyle Huey got [https://bugzilla.mozilla.org/show_bug.cgi?id=1038943 leak detection of B2G mochitests] turned on, after fixing numerous leaks that it detected along the way.
* Thanks to Pin and Jocelyn for jumping on some of the reported leaks.
* This is not exactly MemShrink, but Eric Rahm [https://bugzilla.mozilla.org/show_bug.cgi?id=1027921 improved the deadlock detector] so it runs much faster and uses vastly less memory, which makes debug builds less painful to use.

===Stability (kairo/bsmedberg)===
* Beta crash rate is high due to an adware-related crash that got worsened by trying to fix it (see {{bug|1038243}}). Cause seems to be a forgotten bump of IIDs which will be done in {{bug|1051858}}.

==Team Stand-ups==
(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

===A*team (jgriffin)===



===App Tools (prouget)===



===B2G Services (dougt)===



===Cloud Services (mmayo)===



===Developer Tools (robcee)===



===DOM (jst/overholt)===



===Electrolysis (e10s) (blassey)===



===Firefox Desktop (gavin)===


====Summary of Work In Progress====
* You can find the most recently completed iteration performance report [https://wiki.mozilla.org/Firefox/IterativeDevelopment/IT-34.1PerformanceReport here]
* You can see the status of the current iteration in progress [https://docs.google.com/a/mozilla.com/spreadsheets/d/10sr6YhDNmO4oimlNtxDZ5fe6IaQKmZ7gqT-ZWqAygrI/edit#gid=1914765814 here]
====Summary of Recent Landings====
* Team landed 26 bugs over the last week, for the first half of the 34.2 iteration.
* Details of landings from the past week can be seen [https://bugzilla.mozilla.org/buglist.cgi?f1=flagtypes.name&list_id=10986223&o1=substring&resolution=FIXED&o2=substring&chfieldto=Now&chfield=resolution&query_format=advanced&chfieldfrom=2014-08-05&f2=flagtypes.name&chfieldvalue=FIXED&v1=firefox-backlog&v2=%2B here]

===Firefox Mobile (snorp/blassey/mfinkle)===


====Work In Progress====
*Search activity: Enabled in Nightly! Try it out. See [http://blog.margaretleibovic.com/post/93528710518/firefox-for-android-search-experiments blog post] for some details.
*Tablet refresh: Continuing progress on the tab strip implementation ([https://dl.dropboxusercontent.com/u/1187037/new-tablet.png screenshot]).
** {{bug|1046200}} - Create BrowserApp.isNewTablet()
** {{bug|1047561}} - Create settings UI for enabling the new tablet UI
** {{bug|1048575}} - Disable dynamic toolbar when in new tablet UI
*Janus https://wiki.mozilla.org/Mobile/Janus
**Janus Proxy - Cache improvements
**UI improvements/fixes to addon
You can find more on upcoming feature plans in the[[https://wiki.mozilla.org/Mobile/Roadmap| roadmap]]
===== Nightly ({{CENTRAL_VERSION}})=====
*Allow users to "try again" more than once on new error pages. ([https://bugzilla.mozilla.org/show_bug.cgi?id=910893 Bug 910893 ])
*YouTube HTML5 player does not offer full-screen toggle for embedded YouTube video for Firefox for Android ([https://bugzilla.mozilla.org/show_bug.cgi?id=947841 Bug 947841 ])
*When backspacing the last character of the current page in Firefox for Android's URL bar, it frequently reappears (highlighted, due to autosuggest) and needs to be backspaced again ([https://bugzilla.mozilla.org/show_bug.cgi?id=984057 Bug 984057 ])
*Pasting into url bar does not bring up search screen ([https://bugzilla.mozilla.org/show_bug.cgi?id=1039766 Bug 1039766 ])
*Up scaled and low resolution icons on bookmarks panel, history panel and recent tabs panel ([https://bugzilla.mozilla.org/show_bug.cgi?id=1046579 Bug 1046579 ])
*crash in java.lang.IllegalArgumentException: Property does not exist at org.mozilla.gecko.util.NativeJSObject.getString(Native Method) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1046880 Bug 1046880 ])
*Add ability to stop mirroring a tab ([https://bugzilla.mozilla.org/show_bug.cgi?id=1046971 Bug 1046971 ])
*Take advantage of nsIURIFixup improvements for faster location bar searches ([https://bugzilla.mozilla.org/show_bug.cgi?id=1047607 Bug 1047607 ])
*Only reset search activity when launched from new intent ([https://bugzilla.mozilla.org/show_bug.cgi?id=1048022 Bug 1048022 ])
*Make all empty view images 90x90dp ([https://bugzilla.mozilla.org/show_bug.cgi?id=1048941 Bug 1048941 ])
*Searching for something in search activity it will open a new about:blank page in stead of search results ([https://bugzilla.mozilla.org/show_bug.cgi?id=1049650 Bug 1049650 ])

===Firefox OS Communications (scravag)===



===Firefox OS Connectivity (vchang)===



===Firefox OS Devices/Porting (ericchou)===
{{readonly}}
* Gonk team (led by Thomas Tsai)
** On-site support: Kai-Zen Li @ India (7/28 ~ 8/8)
** [http://goo.gl/fQbpcA Tarako]: Solving gating issues which were reported by Spice/Intex
** [http://goo.gl/fQbpcA Dolphin]: SPRD PTR2 and perf issues
** [http://goo.gl/e015f0 Woodduck]: github code sync and function ready lists
** [http://goo.gl/tHXAE9 Flame]: KK + v1.4/v2.0 porting

* Bluetooth (members: Shawn Huang, Ben Tian, Jamin Liu, Jocelyn Liu)
** {{Bug|1045486}}, {{Bug|1048093}} - Bluetooth transferring doesn't work either when bluetooth backend is BlueZ or Bluedroid - both landed
** {{Bug|1005934}} - Move bluedroid to a separate process (target 2.2)
*** Thomas Zimmermann worked on it and Ben and Shawn are responsible for reviewing.
** The whole team met with Google Chrome OS bt team to discuss about WebBluetooth API.
** Moz's Bluetooth Low Energy API draft - https://workflowy.com/shared/91b7d347-039f-9960-04f9-f1711ad02281/ (WIP)

* Media Playback (members: Bruce Sun, Blake Wu, Star Cheng)
** {{Bug|941302}} - PlatformDecoderModule for Firefox OS - landed (2.1 feat+)
** {{Bug|1009410}} - Expose graphic buffer to MediaCodec - waiting for CAF's response (2.1 feat+)
** {{Bug|1033902}} - Integrate AudioOffloadPlayer with MediaCodecReader and MediaCodecDecoder - reviewing (2.1 feat+)
** {{Bug|1033337}} - [dolphin] It took about 1.8-2.2s for music to start play (It was 1.4+, now 1.4-)
** {{Bug|1049325}} - Last frame is dropped with PlatformDecoderModule enabled - WIP (2.1 feat+)

* Device Storage & Stability (members: Alphan Chen)
** {{Bug|1043264}} - [MTP] Find out the needed MTP API (2.1 feat+)
** {{Bug|1050720}} - "storage-state-change" event will be triggered twice (should be 2.1 feat+)

===Firefox OS Media (slee)===
{{readonly}}
* ImageCaputre API implementation
** WIP
* Support recording media stream from OfflineAudioContext
** WIP
* Intermittent media test cases fixing
** in progress
* [blocker]Video playback doesn't start and buffering icon is seen forever
** analyzing
* async codec threading part
** reviewing

===Firefox OS Media Apps (hema)===



===Firefox OS Media Recording(pchang)===



===Firefox OS Performance (mlee)===



===Firefox OS Productivity (doliver)===



===Firefox OS RIL (htsai)===

{{readonly}}
#https://wiki.mozilla.org/TPE_RIL_team/2014-08-12

===Firefox OS Systems - Front End (gwagner)===



===Firefox OS Systems - Platform (timdream)===



===GFX (milan)===



===JS (naveed)===
{{readonly}}

* Intern Work Completed
Implemented ES6 template strings - bug 1021368, bug 1024748, bug 1031397, bug 1034314, bug 1038259, bug 1038498
Implemented ES6 String.raw and ToLength (self-hosted) - bug 1039774 and bug 1040196
Implemented ES6 computed property names - bug 924688

* Compiler (JIT)
** {{bug|1039458}}: landed basic loop unrolling
** {{bug|1042833}}: removed JS_ION entirely

* Garbage Collection
** {{bug|650161}}: Compacting GC
*** currently it supports moving JSObjects only
*** most tests pass now but there are still some bugs to iron out
*** posted initial set of patches for review

* Front End and Other
** SharedArrayBuffer: cleaned up lock/futex POC code and spec somewhat
** {{bug|1047220}}: Shrink the static atoms table

===Layout (jet/dbaron)===

{{readonly}}
Some bugs of note:
*{{bug|996796}} Lots of style infrastructure for better animations and transitions
*{{bug|1018278}} Blacklist some Intel graphics drivers
*{{bug|927892}} Working on HTML5 Canvas filters

===Media (mreavy)===

{{readonly}}
* Windowsharing now refreshes the window list on each request - {{bug|1041369}} - thanks to new contributor Roman Skalish
** On windows, it offers to share some uninteresting windows at times, like the sharing indicator or the Windows menu
* GMP OpenH264 Mode 0 supported - {{bug|1051566}} - thanks to new contributor Mo Zanaty for providing fixes for the underlying webrtc.org code
* Windows OpenH264 IPC crash resolved ({{bug|1044245}})
* Aurora/33 updated with all important Screensharing and OpenH264 fixes

===Necko (dougt/jduell)===

{{readonly}}

* HTTP/2 on nightly wouldn't work with Twitter for a little while--mostly their fault.
* {{bug|1007020}} - XHR Progress Events need a way to read how many compressed bytes have been downloaded
* Getting closer to landing Resource Timing API
** {{bug|1047848}} - PerformanceResourceTiming objects can't be JSON.stringify'd
* Making progress on captive portal detection.

===Performance (vladan)===



===Seceng (keeler)===



{{Bug|1036546}} landed: soft-disable proprietary window.crypto functions/properties before removing them entirely (things like window.crypto.generateCRMFRequest now don't exist unless the pref "dom.unsafe_legacy_crypto.enabled" is true). See also {{Bug|1030963}}.

===Shumway (tschneidereit)===



===WebAPI (overholt)===



==Roundtable==
(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

==<Read only beyond this point>==

===Friends of the Tree===

===Mailing List Threads===
(Threads that are likely to be of interest to engineering from various mailing lists.)

===Good Reads===
(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
</pre>