Gaia/Meeting/2014-07-15: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "Weekly Gaia Development Meeting * Date: 2014-07-08 * https://etherpad.mozilla.org/gaia-meeting-notes * Meeting connection details: https://wiki.mozilla.org/B2G#Meetings * Host...")
 
No edit summary
 
Line 1: Line 1:
Weekly Gaia Development Meeting
Weekly Gaia Development Meeting
* Date: 2014-07-08
* Date: 2014-07-15
* https://etherpad.mozilla.org/gaia-meeting-notes
* https://etherpad.mozilla.org/gaia-meeting-notes
* Meeting connection details: https://wiki.mozilla.org/B2G#Meetings
* Meeting connection details: https://wiki.mozilla.org/B2G#Meetings
* Host: aus
* Host: Hub
* Minutes copied to the wiki by host each week https://wiki.mozilla.org/Gaia/Meeting_Notes
* Minutes copied to the wiki by host each week https://wiki.mozilla.org/Gaia/Meeting_Notes
==Announcements & Notices==
==Announcements & Notices==
Add your workweeks, new hires, other announcements:
Add your workweeks, new hires, other announcements:
[Julien] You do stand-up/daily meetings? You should read this: http://martinfowler.com/articles/itsNotJustStandingUp.html
* [nhirata] Bugbash for flame 273Mb that was planned for this week is pushed to next week: July 24th
[nhirata] Bugbash for flame 273Mb that was planned for this week is pushed to next week: July 24th
* [doliver] Lots of 2.0 blockers! (79 at the moment) Some teams have free cycles -if you have a bug that is appropriate for someone outside of your team  to fix, please add guidance to the bug on the probable cause and/or fix  and let everyone know that it's open for taking
== Round Table ==
 
* [Julien] Travis vs Gaia Try
==Roundtable==
** can we move some or all already? what's missing?
 
** if we still stay on Travis for some time, we need people who care (part-time sheriff). Role consist of:
* [nhirata] should QA ask releng to build a 256 MB build for flame and then test off of that for 256 MB testing?
*** backout if there is new red
** this is in regards to GAIA_MEMORY_PROFILE=256 build time variable which affects gallery.  Not sure where else it would affect.  (bug 1024692) Camera is done elsewhere.
*** if it's difficult to find the culprit, filing bugs instead, and following up
** Tarako had a GAIA_MEMORY_PROFILE=low variable
*** main goal is to always be green
** [Kevin] A 256 flame is not a valid reference device. No one will ship a device at that resolution with that memory footprint. (Discussion ongoing  in drivers if this is a valid target or not)
*** some code to be done sometimes, to fix our tools
*** CAF request : see bug 1024692 comment 67: https://bugzilla.mozilla.org/show_bug.cgi?id=1024692#c67
** who's deciding when we move to Gaia Try ?[Francisco] We need an action on a hard date to move to just gaia-try
** discussion thread going on in email about 256 MB testing in general being a waste of engineering resources?
** [Kevin] Intermittent tests
 
*** In-tree config for solving intermittent tests.
* [Kevin] Update on gaia JS Marionette tests:
*** Should we disable intermittent failures and re-enable Gi on TBPL?
** Renamed on TBPL, now 'Gij'
** Action items:
** Intermittent test rate is now good on tbpl, < 2% failure rate for tests.
*** Intermittent tests will be disabled on Friday (July 11th)
** Only blocker to re-enable Gij on TBPL is due to harness issues:
*** Gi re-enabled early next week.
*** https://bugzilla.mozilla.org/show_bug.cgi?id=1037924
*** mail sent by Julien to the ML
*** Looking for help on this one.
* [Julien] 1.3t+ bugs were not autoapproved for 1.4. Some/most of them obviously needed to go to 1.4 too, and doing it several weeks after is a pain. What was the rationale to do this? Should it be done the same way for the next long-lived device-specific branch? (In the comms team, we think it was a mistake)
** gaia-try was down this morning - do we need sheriffs involved to monitor?
** [jsmith] I think the main reason was that some 1.3T+ bugs were deemed too risky to auto-land onto 1.4, so we need to be conscious of risk on landings for 1.4. We need to stabilize 1.4 by end of July, so we have to be careful of what can land.
*** Tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1038732
** [jsmith] We are trying to avoid another long-lived device-specific branch in the future by enforcing a requirement in 2.0 that mainline release branches need to be chipset independent.
 
** [julien] (I was more talking about the patches landing both in master and 1.3t+, not 1.3t+ specific patch)
==QA==
** jsmith will discuss with Bhavana about this and look at remaining 1.3t+ blockers.
Reporter: nhirata updated 7/15; jsmith on PTO this week, 2 work weeks happening; qa on lower resources this week
* [Francisco] Uplifting patches to branches in some cases breaks that branch, we have recently v1.4 perma-red
* [Julien] The notes in the wiki are ugly: ex: https://wiki.mozilla.org/Gaia/Meeting/2014-06-24 Who is responsible for copying this to the wiki, and how can we help to make this better?
** [benfrancis] It's usually the meeting host (or me) who copies this across from the Etherpad at the end of the meeting. Making it prettier would require someone who cares enough to change Etherpad format to MediaWiki wiki markup each week.
** Action: Switch to using MediaWiki formatting in Etherpad for Gaia Meeting Notes.
   
* [jsmith] Developing for 273 MB Flame as a primary development environment
** Note - QA is trying to get 273 MB Flame stable, so this would happen post getting the 273 MB Flame build to be usable.
*** [benfrancis] How representative of an actual 256MB device is this, given graphics hardware differences etc.?
*** [jsmith] My understanding from the discussion with the chipset vendor in question was that this was the closest solution we have right now to their 256 MB reference device they are using for certification testing (see https://bugzilla.mozilla.org/show_bug.cgi?id=1008050#c22)
*** Action: Memory + Processing power is a big factor in testing and passing certification, developers should test on at least one low memory device before committing patches. We will try and come up with a better long term strategy for this over the coming weeks.
==QA==  
Reporter: nhirata updated 7/15
* 1.4
* 1.4
** QA Wanted, smoketesting, and Dolphin-specific test run support
** QA Wanted, smoketesting, and Dolphin-specific test run support
Line 47: Line 36:
** 14 open blocking bugs : http://mzl.la/1mdZPZu
** 14 open blocking bugs : http://mzl.la/1mdZPZu
** 17 1.4? nomed bugs : http://mzl.la/1qDrWW5
** 17 1.4? nomed bugs : http://mzl.la/1qDrWW5
* 2.0
* 2.0
** QA Wanted, smoketesting, and full test run support
** QA Wanted, smoketesting, and full test run support
Line 58: Line 48:
**** https://bugzilla.mozilla.org/show_bug.cgi?id=1037556
**** https://bugzilla.mozilla.org/show_bug.cgi?id=1037556
**** patch in bug
**** patch in bug
** Loc Run active - planned to run until Wednesday, keep a look out for localization bugs
** Loc Run finished : Theo Chevalier sent out an email with the results:
*** 2nd round will begin on July 31st.
** Bugbash for flame 273Mb that was planned for this week is pushed to next week: July 24th
** Bugbash for flame 273Mb that was planned for this week is pushed to next week: July 24th
**  2.0 Exploratory Test Run against 273MB being currently done
**  2.0 Exploratory Test Run against 273MB being currently done
** 2 testers on FMD exploratory testing
*** 2 testers on FMD exploratory testing
** QA Plan to get 273 MB Flame under control
** QA Plan to get 273 MB Flame under control
*** Part 1 - Sanity Tests (~10 tests) + 2 hours daily exploratory testing by major area on a per day basis (M - Comms, T - Media, W - System, TR - Productivity, F - Misc) on 273 MB Flame
*** Part 1 - Sanity Tests (~10 tests) + 2 hours daily exploratory testing by major area on a per day basis (M - Comms, T - Media, W - System, TR - Productivity, F - Misc) on 273 MB Flame
Line 69: Line 60:
*** Part 3 - All testing migrated to 273 MB Flame
*** Part 3 - All testing migrated to 273 MB Flame
*** Bug Query - http://mzl.la/1kxNjEv
*** Bug Query - http://mzl.la/1kxNjEv
* 2.1
* 2.1
** QA Wanted & smoketesting support
** QA Wanted & smoketesting support
Line 79: Line 71:
**** waiting for https://bugzilla.mozilla.org/show_bug.cgi?id=1031369 to land
**** waiting for https://bugzilla.mozilla.org/show_bug.cgi?id=1031369 to land
==Support==
==Support==
*
 
Updates:
 
==TEAM UPDATES==
==TEAM UPDATES==
=== Productivity ===
=== Productivity ===
Talking this week:  
Talking this week:  
Sprint tracking wiki: https://wiki.mozilla.org/FirefoxOS/productivity
Sprint tracking wiki: https://wiki.mozilla.org/FirefoxOS/productivity
Notes: https://etherpad.mozilla.org/fxos-productivity
Notes: https://etherpad.mozilla.org/fxos-productivity
The Team: asuth, evanxd, gaye, lightsofapollo, doliver, jrburke, mcav, millermedeiros, awiss, jhford, cserran, tony (qa), william hsu (qa), jhuang (ux), harly (ux)
The Team: asuth, evanxd, gaye, lightsofapollo, doliver, jrburke, mcav, millermedeiros, awiss, jhford, cserran, tony (qa), william hsu (qa), jhuang (ux), harly (ux)
Updates:
=== Media front end ===
=== Media front end ===
Talking this week:  
Talking this week:  
* Our  team: Dave Hylands, David Flanagan, Mike Habicher, Jim Porter, Hema    Koka, Dominic Kuo, John Hu, Diego Marcos, Wilson Page, Justin  D'Arcangelo , Punam Dahiya (part-time), Russ Nicoletti (part-time)  Product: Sri Kasetti Ux:  Rob  MacDonald, Patryk Adamczyk EPM: Candice  Serran QA: Marcia Knous
* Our  team: Dave Hylands, David Flanagan, Mike Habicher, Jim Porter, Hema    Koka, Dominic Kuo, John Hu, Diego Marcos, Wilson Page, Justin  D'Arcangelo , Punam Dahiya (part-time), Russ Nicoletti (part-time)  Product: Sri Kasetti Ux:  Rob  MacDonald, Patryk Adamczyk EPM: Candice  Serran QA: Marcia Knous
Updates:
=== Performance (read only) ===
=== Performance (read only) ===
Talking this week:  
TEAM: eli, geo, hub, huseby, jhylands, mchang, mlee, wlach, Walter Chen
Wiki: https://wiki.mozilla.org/FirefoxOS/Performance
Sprints: http://scrumbu.gs/p/fxos-perf/
Updates:


    TEAM: eli, geo, hub, huseby, jhylands, mchang, mlee, wlach, Walter Chen
* Team work week in Paris next week


    Sites
=== Comms app ===
Talking this week:
Updates:


    Wiki: https://wiki.mozilla.org/FirefoxOS/Performance
    Sprints: http://scrumbu.gs/p/fxos-perf/
    Updates:
=== Comms app ===
Talking this week: Julien
* End of a sprint, start of a new one
* All visual refresh bugs landed and uplifted
* blocker count is low
* Demos for the SMS app: https://wiki.mozilla.org/Gaia/SMS/Scrum/4#Demos
* Sprint links:
** SMS app: https://wiki.mozilla.org/Gaia/SMS/Scrum
** Contacts app: https://wiki.mozilla.org/Gaia/Contacts/Scrum/2.0S6
** Dialer app: https://wiki.mozilla.org/FirefoxOS/Comms/Dialer/Sprint/v2.0-S6
=== Systems front end ===
=== Systems front end ===
Talking this week: Michael H
Talking this week:  
Sprint tracking wiki: https://wiki.mozilla.org/FirefoxOS/systemsfe
Sprint tracking wiki: https://wiki.mozilla.org/FirefoxOS/systemsfe
Daily standups: https://etherpad.mozilla.org/fxos-systems-frontend2-0
Daily standups: https://etherpad.mozilla.org/fxos-systems-frontend2-0
The team: cserran, gwagner, qdot, michael h, aus, alexandre, francis, jason, pdol, benfrancis, daleharvey, gmarty, sfoster, naoki, tef, tedders1, Cwiiis
The team: cserran, gwagner, qdot, michael h, aus, alexandre, francis, jason, pdol, benfrancis, daleharvey, gmarty, sfoster, naoki, tef, tedders1
Updates:
Updates:
* Stabalization for 2.0, like everyone
* Background collections
* Updates to FTE tutorial
* Starting to ramp up Rocketbar for 2.1, fixing regressions caused by homescreen search https://bugzilla.mozilla.org/show_bug.cgi?id=1035868
==OPTIONAL UPDATES==
=== System platform ===
=== RIL ===
=== Media recording ===
=== Device ===
== Round Table ==

Latest revision as of 19:09, 15 July 2014

Weekly Gaia Development Meeting

Announcements & Notices

Add your workweeks, new hires, other announcements:

  • [nhirata] Bugbash for flame 273Mb that was planned for this week is pushed to next week: July 24th
  • [doliver] Lots of 2.0 blockers! (79 at the moment) Some teams have free cycles -- if you have a bug that is appropriate for someone outside of your team to fix, please add guidance to the bug on the probable cause and/or fix and let everyone know that it's open for taking

Roundtable

  • [nhirata] should QA ask releng to build a 256 MB build for flame and then test off of that for 256 MB testing?
    • this is in regards to GAIA_MEMORY_PROFILE=256 build time variable which affects gallery. Not sure where else it would affect. (bug 1024692) Camera is done elsewhere.
    • Tarako had a GAIA_MEMORY_PROFILE=low variable
    • [Kevin] A 256 flame is not a valid reference device. No one will ship a device at that resolution with that memory footprint. (Discussion ongoing in drivers if this is a valid target or not)
    • discussion thread going on in email about 256 MB testing in general being a waste of engineering resources?

QA

Reporter: nhirata updated 7/15; jsmith on PTO this week, 2 work weeks happening; qa on lower resources this week

  • 1.4
  • 2.0
    • QA Wanted, smoketesting, and full test run support
    • 61/62 smoketests passing,3 blockers (Flame 512 MB) on the same smoke test
    • Loc Run finished : Theo Chevalier sent out an email with the results:
      • 2nd round will begin on July 31st.
    • Bugbash for flame 273Mb that was planned for this week is pushed to next week: July 24th
    • 2.0 Exploratory Test Run against 273MB being currently done
      • 2 testers on FMD exploratory testing
    • QA Plan to get 273 MB Flame under control
      • Part 1 - Sanity Tests (~10 tests) + 2 hours daily exploratory testing by major area on a per day basis (M - Comms, T - Media, W - System, TR - Productivity, F - Misc) on 273 MB Flame
        • Exit Criteria - Green Sanity Tests for 3 Days
      • Part 2 - Manual Smoke Tests (~44 tests) on 273 MB Flame
        • Exit Criteria - Green Smoke Tests for 3 Days
      • Part 3 - All testing migrated to 273 MB Flame
      • Bug Query - http://mzl.la/1kxNjEv

Support

Updates:

TEAM UPDATES

Productivity

Talking this week: Sprint tracking wiki: https://wiki.mozilla.org/FirefoxOS/productivity Notes: https://etherpad.mozilla.org/fxos-productivity The Team: asuth, evanxd, gaye, lightsofapollo, doliver, jrburke, mcav, millermedeiros, awiss, jhford, cserran, tony (qa), william hsu (qa), jhuang (ux), harly (ux) Updates:

Media front end

Talking this week:

  • Our team: Dave Hylands, David Flanagan, Mike Habicher, Jim Porter, Hema Koka, Dominic Kuo, John Hu, Diego Marcos, Wilson Page, Justin D'Arcangelo , Punam Dahiya (part-time), Russ Nicoletti (part-time) Product: Sri Kasetti Ux: Rob MacDonald, Patryk Adamczyk EPM: Candice Serran QA: Marcia Knous

Updates:

Performance (read only)

TEAM: eli, geo, hub, huseby, jhylands, mchang, mlee, wlach, Walter Chen Wiki: https://wiki.mozilla.org/FirefoxOS/Performance Sprints: http://scrumbu.gs/p/fxos-perf/ Updates:

  • Team work week in Paris next week

Comms app

Talking this week: Updates:

Systems front end

Talking this week: Sprint tracking wiki: https://wiki.mozilla.org/FirefoxOS/systemsfe Daily standups: https://etherpad.mozilla.org/fxos-systems-frontend2-0 The team: cserran, gwagner, qdot, michael h, aus, alexandre, francis, jason, pdol, benfrancis, daleharvey, gmarty, sfoster, naoki, tef, tedders1 Updates: