MozillaWiki

Platform/2014-11-25: Difference between revisions

Page Discussion

Platform/2014-11-25 (view source)

Revision as of 19:19, 25 November 2014

2,642 bytes added ,  25 November 2014
→‎Roundtable: link to Portland schedules
(→‎Roundtable: link to Portland schedules)
 
(13 intermediate revisions by 11 users not shown)
Line 17: Line 17:
<small>(Release and system issues that may impact engineering this week.)</small>
<small>(Release and system issues that may impact engineering this week.)</small>


===Notices/Schedule (lsblakk/sylvestre/lmandel)===
===Notices/Schedule (lmandel)===
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"
|-
|-
Line 35: Line 35:
<!-- 2. What will your team do this week that might impact others? -->
<!-- 2. What will your team do this week that might impact others? -->
<!-- 3. Is anything slowing your team down or getting in their way? -->
<!-- 3. Is anything slowing your team down or getting in their way? -->
34 Desktop:
* 34.0 Desktop RC build1 yesterday has a few outstanding issues so...
* 34.0 Desktop RC build2 gtb today
* 34.0.5 Desktop RC gtb as soon as we have the search information we need
34 Mobile:
* 34.0 Mobile RC build done! Just waiting for release day.
* 34 betas are done. Only request tracking if you have a stop ship bug or want to consider a bug for a ride-along in a point release (if we have one)
* Firefox 34 scheduled to release on Mon, Dec 1.
* Reminder that the merge is taking place this Fri, Nov 28
Next beta:
* Firefox 35 beta1 ships Dec 4
Work week sessions:
* Wed, 2-3 (Medford room)- Shorter release cycles
** Agenda: http://relman.etherpad.mozilla.org/shorter-release-cycles-ww2014
* Thu, 11-12 (Ballroom F pipe and drape) - Measuring/Identifying issues and better understanding releases
** Agenda: http://relman.etherpad.mozilla.org/measuring-identifying-issues-ww2014
* Thu, 2-3 (Portland room) - Responding/issue mitigation for releases
** Agenda: http://relman.etherpad.mozilla.org/responding-issues-ww2014
* Thu, 3-4 (Oregon Ballroom) - Intermittent Orange (A-Team Session)
* Also looking to schedule time to speak with each team about our release process.


===Build Changes (gps)===
===Build Changes (gps)===
Line 65: Line 92:


===OrangeFactor (ryanvm)===
===OrangeFactor (ryanvm)===
 
{{readonly}}
<!-- Read only update this week? Uncomment the following line-->
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 2.66] (last week: 2.33).
<!-- {{readonly}} -->
** Something's wrong with these numbers. Investigating.
 
* 26 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-11-18&f1=cf_last_resolved&query_format=advanced&list_id=11629396 List] - Thanks!.
<!-- 1. What has your team done since last week that might impact others? -->
** Thanks to Dave Townsend (:Mossop) for fixing some frequent and long-standing Addon Manager oranges
<!-- 2. What will your team do this week that might impact others? -->
<!-- 3. Is anything slowing your team down or getting in their way? -->
 


===CritSmash (dbolter)===
===CritSmash (dbolter)===
Line 87: Line 111:


<!-- Read only update this week? Uncomment the following line-->
<!-- Read only update this week? Uncomment the following line-->
<!-- {{readonly}} -->
{{readonly}}


<!-- 1. What has your team done since last week that might impact others? -->
<!-- 1. What has your team done since last week that might impact others? -->
Line 93: Line 117:
<!-- 3. Is anything slowing your team down or getting in their way? -->
<!-- 3. Is anything slowing your team down or getting in their way? -->


No update.


===Stability (kairo)===
===Stability (kairo)===


<!-- Read only update this week? Uncomment the following line-->
<!-- Read only update this week? Uncomment the following line-->
<!-- {{readonly}} -->
{{readonly}}


<!-- 1. What has your team done since last week that might impact others? -->
<!-- 1. What has your team done since last week that might impact others? -->
Line 103: Line 128:
<!-- 3. Is anything slowing your team down or getting in their way? -->
<!-- 3. Is anything slowing your team down or getting in their way? -->


* [http://arewestableyet.com/ Overall numbers] are looking good except desktop Nightly, which is on a down trend as well.


==Team Stand-ups==
==Team Stand-ups==
Line 209: Line 235:


===Firefox Mobile (snorp/blassey/mfinkle)===
===Firefox Mobile (snorp/blassey/mfinkle)===
 
*MP3 audio playback on Android L
<!-- Read only update this week? Uncomment the following line-->
<!-- {{readonly}} -->
 
<!-- 1. What has your team done since last week that might impact others? -->
<!-- 2. What will your team do this week that might impact others? -->
<!-- 3. Is anything slowing your team down or getting in their way? -->
 


===GFX (milan)===
===GFX (milan)===
Line 241: Line 260:


<!-- Read only update this week? Uncomment the following line-->
<!-- Read only update this week? Uncomment the following line-->
<!-- {{readonly}} -->
{{readonly}}


<!-- 1. What has your team done since last week that might impact others? -->
1. What has your team done since last week that might impact others?
<!-- 2. What will your team do this week that might impact others? -->
* Landed display:contents
<!-- 3. Is anything slowing your team down or getting in their way? -->
* Bug 1074528 - Implement parsing/computing of inset()


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


===Media (mreavy)===
===Media (mreavy)===


<!-- Read only update this week? Uncomment the following line-->
<!-- Read only update this week? Uncomment the following line-->
<!-- {{readonly}} -->
{{readonly}}


<!-- 1. What has your team done since last week that might impact others? -->
<!-- 1. What has your team done since last week that might impact others? -->
* Fixes to Block & Cancel done and uplifted
<!-- 2. What will your team do this week that might impact others? -->
<!-- 2. What will your team do this week that might impact others? -->
* Rooms on Aurora should be enabled tonight
<!-- 3. Is anything slowing your team down or getting in their way? -->
<!-- 3. Is anything slowing your team down or getting in their way? -->


===Necko (dougt/jduell)===
===Necko (dougt/jduell)===
Line 262: Line 285:
<!-- Read only update this week? Uncomment the following line-->
<!-- Read only update this week? Uncomment the following line-->
<!-- {{readonly}} -->
<!-- {{readonly}} -->
* Looking into the HTTPS/TLS feature set of our new search partners: short answer is they're behind Google on some issues.
* figured out why our patch fails on B2G emulator


<!-- 1. What has your team done since last week that might impact others? -->
<!-- 1. What has your team done since last week that might impact others? -->
<!-- 2. What will your team do this week that might impact others? -->
<!-- 2. What will your team do this week that might impact others? -->
<!-- 3. Is anything slowing your team down or getting in their way? -->
<!-- 3. Is anything slowing your team down or getting in their way? -->


===Performance (vladan)===
===Performance (vladan)===
Line 273: Line 298:
<!-- {{readonly}} -->
<!-- {{readonly}} -->


<!-- 1. What has your team done since last week that might impact others? -->
1. What has your team done since last week that might impact others?
<!-- 2. What will your team do this week that might impact others? -->
 
<!-- 3. Is anything slowing your team down or getting in their way? -->
* Firefox responsiveness metric:
** We landed a Telemetry probe that measures delay in ms between the target and the actual handling time of the frame at refresh driver
*** http://mzl.la/1zRFtOP
* Looked at BHR data to determine how common are plugin hangs:
** Preliminary data from one day on Nightly (not reliable!): https://etherpad.mozilla.org/tKgLhkkTVe
** More reliable data from Aurora: http://robertovitillo.com/2014/11/25/clustering-firefox-hangs/
** These numbers help set expectations for benefits of aklotz's async plugin init patch & Shumway work
 
2. What will your team do this week that might impact others?


* Portland: Roberto will hold a tutorial on analyzing Telemetry data using Spark, a much faster way to do custom analyses of large amounts of Telemetry data
** Date & location will be posted on m.d.platform
* {{bug|1076775}}: Working on removing jank from the new "Forget History button" feature


===Seceng (dougt)===
===Seceng (dougt)===
Line 310: Line 346:
==Roundtable==
==Roundtable==
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small>
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small>
* Is BHR data for Desktop available somewhere?
* Portland work week schedules:
** [https://docs.google.com/a/mozilla.com/spreadsheets/d/1soTlx3uIBaWMSCA-tHyclkX2aV7q70Z3nJe5JWUXVDg/edit#gid=0 Platform Eng and Platform Ops Org]
** [https://docs.google.com/a/mozilla.com/spreadsheets/d/12K2OIUKAURjtQOcOMcPCOi4qeB1i80UWCA4EZLX94b4/edit#gid=0 Portland room blocks for teams]


==<Read only beyond this point>==
==<Read only beyond this point>==
Cpeterson
Confirmed users
3,314

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1036200...1036707"