Platform/2014-12-16: Difference between revisions

 
(7 intermediate revisions by 7 users not shown)
Line 32: Line 32:
|}
|}


* 35.0b4 shipping today
* 35.0b4 looking like we'll do a build 2 with backout {{bug|1097321}} due to startup crash issues in b3
* Major stability issues with 35 right now (both graphics)
 
** {{bug|1074378}} and {{bug|1098597}} -- looks like we need to backout {{bug|1097321}}
* 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
 


<!-- 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 104: Line 109:
<!-- 3. Is anything slowing your team down or getting in their way? -->
<!-- 3. Is anything slowing your team down or getting in their way? -->


* 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==
==Team Stand-ups==
Line 109: Line 115:


===A*Team (jgriffin)===
===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]


<!-- Read only update this week? Uncomment the following line-->
<!-- Read only update this week? Uncomment the following line-->
Line 116: Line 127:
<!-- 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? -->


===Accessibility (dbolter)===
===Accessibility (dbolter)===
Line 199: Line 209:
* Please help test e10s in Nightly!
* Please help test e10s in Nightly!
** Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect
** 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 Desktop (gavin)===
Line 232: Line 243:
===JS (naveed)===
===JS (naveed)===


<!-- Read only update this week? Uncomment the following line-->
{{readonly}}
<!-- {{readonly}} -->
* 2015 Layout Roadmap posted:
 
** https://wiki.mozilla.org/Platform/Roadmap#JavaScript
<!-- 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? -->
 


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


<!-- Read only update this week? Uncomment the following line-->
<!-- Read only update this week? Uncomment the following line-->
<!-- {{readonly}} -->
{{readonly}}
 
* 2015 Layout Roadmap posted:
<!-- 1. What has your team done since last week that might impact others? -->
** https://wiki.mozilla.org/Platform/Roadmap#Layout
<!-- 2. What will your team do this week that might impact others? -->
<!-- 3. Is anything slowing your team down or getting in their way? -->
 


===Media (mreavy)===
===Media (mreavy)===
Line 275: Line 279:
** we'll advertise final (non-draft) HTTP/2 support in 36
** we'll advertise final (non-draft) HTTP/2 support in 36
** opportunistic encryption will be in 37
** 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


<!-- 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 337: Line 344:
===irc #planning Log From This Meeting===
===irc #planning Log From This Meeting===
<pre style="white-space:pre-wrap;">
<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>
</pre>
Confirmed users
204

edits