Firefox/Go Faster/Meetings/20150818: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(aug 18 minutes)
 
Line 7: Line 7:


== Attendees ==
== Attendees ==
*  
* Larissa
* Laura
* Axel
* Jonathan
* Tarek
* bhearsum
* margaret
* mbrandt
* edwong
* rnewman
* telliott
* mossop
* sylvestre
* krupa


= Agenda =
== Agenda ==


== Discuss Q3 goal updates per team: ==
=== Discuss Q3 goal updates per team: ===
*Client integration (Mossop/rhelmer)
* Client integration (Mossop/rhelmer)  
*Build pipeline (mrrrgn)
** much distraction from security bugs (mossop)
*Test automation (mbrandt or jgriffin)  
** working on hello addon, pdf.js or shumway will work for pipeline testing and he can provide a zippy to anyone who needs one(rhelmer)
*IdeaTown (nchapman/jgruen)
* Build pipeline (mrrrgn)  
*Updates (tarek)  
** still on PTO
*Fat Fennec (richard)
* Test automation (mbrandt or jgriffin
*l10n (axel)
** need support from the release pipeline for treeherder
* QA (krupa)
** test plan in active development almost ready to share
* IdeaTown (nchapman/jgruen)  
** teaser site launch pending product and marketing go-to-market plan (timing?)
** now with more officialness!
** 1.0 launch src here: https://github.com/mozilla/idea-town
* Updates (tarek)
** security settings:
*** server-side: working on notifications
*** client-side: mark's back this week
* Fennec "OTA" updates
** designing the client-server interaction (draft should be ready this week)
* Fat Fennec (richard)  
** Margaret and I have two folks working on pulling different threads: sebastian on fonts, jonalmeida on hyph.
** rnewman will be working with tarek on the client-server spec as soon as iOS is out the door.
* l10n (axel)  
** "its more like figuring out if there are goals, than naming the goals"
** the closer we can keep to the normal firfox tooling the better, for l10n


== Roundtable and Q&A ==
=== Roundtable and Q&A ===
* PRD out for review!
* PRD out for review!  
* L10N strategy
* l10n strategy discussion
*
* How do we avoid having many branches for system addons? We may limit the channels they are applied to or test and then turn them off to channels they dont work in  - likely only beta and release. how do we then not exclude dev edition?


== Actions: ==
=== Actions: ===
*
* mbrandt/larissa/krupa circile back on QA
== Administrivia:==
* Work with krupa to get a draft of the test plan in circulation to the group for review and comment
* Toby help Axel with l10n strategy
* Please read the PRD and write comments! If you need a link, ask Larissa
 
== Administrivia: ==


* Mailing list! If you're not on it, please add yourself: https://mail.mozilla.org/listinfo/gofaster
* Mailing list! If you're not on it, please add yourself: https://mail.mozilla.org/listinfo/gofaster
 
* Weekly status reports go to that list around Wednesday of each week and are archived on the wiki.
** Weekly status reports go to that list around Wednesday of each week and are archived on the wiki.  
* Please use our shiny tracking bugs to track your work:
 
** https://bugzil.la/1184527: [Go Faster] Q3 Goal Tracking - Ship v1 of Firefox Experiments / Idea Town  
* Please use our shiny tracking bugs to track your work:  
** https://bugzil.la/1184524: [Go Faster] Q3 Goal Tracking - Implement lightweight build, test, and release pipeline for go-faster
 
** https://bugzil.la/1183866: [Go Faster] Q3 tracking - Client support for system add-ons install and update
** https://bugzil.la/1184527: [Go Faster] Q3 Goal Tracking - Ship v1 of Firefox Experiments / Idea Town  
** https://bugzil.la/1184528: [Go Faster] Q3 Goal Tracking - Security policy updates through new update service ("Balrog 2.0")
** https://bugzil.la/1184524: [Go Faster] Q3 Goal Tracking - Implement lightweight build, test, and release pipeline for go-faster  
** https://bugzil.la/1183866: [Go Faster] Q3 tracking - Client support for system add-ons install and update  
** https://bugzil.la/1184528: [Go Faster] Q3 Goal Tracking -Security policy updates through new update service ("Balrog 2.0")

Latest revision as of 23:10, 21 August 2015

= August 18, 2015

Meeting details

Attendees

  • Larissa
  • Laura
  • Axel
  • Jonathan
  • Tarek
  • bhearsum
  • margaret
  • mbrandt
  • edwong
  • rnewman
  • telliott
  • mossop
  • sylvestre
  • krupa

Agenda

Discuss Q3 goal updates per team:

  • Client integration (Mossop/rhelmer)
    • much distraction from security bugs (mossop)
    • working on hello addon, pdf.js or shumway will work for pipeline testing and he can provide a zippy to anyone who needs one(rhelmer)
  • Build pipeline (mrrrgn)
    • still on PTO
  • Test automation (mbrandt or jgriffin)
    • need support from the release pipeline for treeherder
  • QA (krupa)
    • test plan in active development almost ready to share
  • IdeaTown (nchapman/jgruen)
  • Updates (tarek)
    • security settings:
      • server-side: working on notifications
      • client-side: mark's back this week
  • Fennec "OTA" updates
    • designing the client-server interaction (draft should be ready this week)
  • Fat Fennec (richard)
    • Margaret and I have two folks working on pulling different threads: sebastian on fonts, jonalmeida on hyph.
    • rnewman will be working with tarek on the client-server spec as soon as iOS is out the door.
  • l10n (axel)
    • "its more like figuring out if there are goals, than naming the goals"
    • the closer we can keep to the normal firfox tooling the better, for l10n

Roundtable and Q&A

  • PRD out for review!
  • l10n strategy discussion
  • How do we avoid having many branches for system addons? We may limit the channels they are applied to or test and then turn them off to channels they dont work in - likely only beta and release. how do we then not exclude dev edition?

Actions:

  • mbrandt/larissa/krupa circile back on QA
  • Work with krupa to get a draft of the test plan in circulation to the group for review and comment
  • Toby help Axel with l10n strategy
  • Please read the PRD and write comments! If you need a link, ask Larissa

Administrivia:

  • Mailing list! If you're not on it, please add yourself: https://mail.mozilla.org/listinfo/gofaster
  • Weekly status reports go to that list around Wednesday of each week and are archived on the wiki.
  • Please use our shiny tracking bugs to track your work: