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

From MozillaWiki
Jump to navigation Jump to search
(adding minutes)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
= August 25, 2015 =
= September 1, 2015 =
== Meeting details ==
== Meeting details ==
* Tuesdays @1630GMT/1230 EDT/0930PDT  
* Tuesdays @1630GMT/1230 EDT/0930PDT  
Line 13: Line 13:


=== Discuss Q3 goal updates per team: ===
=== Discuss Q3 goal updates per team: ===
* Client integration (Mossop/rhelmer)  
* Client integration (Mossop/rhelmer)
* Build pipeline (mrrrgn)  
** patch for loading system addons is in Rob's queue to review now
** following that is work to request new system addons
** hello is now working as a prototype addon
** https://bugzilla.mozilla.org/show_bug.cgi?id=1186172#c7
* Build pipeline (mrrrgn out, JP present)  
** JP getting reacquainted, learning task cluster. 
* Test automation (mbrandt or jgriffin)   
* Test automation (mbrandt or jgriffin)   
** still on hold
* QA (krupa)
* QA (krupa)
* IdeaTown (nchapman/jgruen/edwong)   
** Krupa out but her QA plan will hit the wiki this week
* IdeaTown (nchapman/jgruen/edwong)  
**    
* Updates (tarek)
* Updates (tarek)
* Fennec "OTA" updates
**
* Fat Fennec (richard)  
* Fat Fennec (richard)  
**
* l10n (axel)  
* l10n (axel)  
* Other teams present?
**


=== Roundtable and Q&A ===
=== Roundtable and Q&A ===
* Release Pipeline next steps - Laura's proposal from the list:
* Release Pipeline next steps - Laura's proposal from the list:
1. Since we have a) Client support for Go-Faster add-ons landing next
**  Since we have a) Client support for Go-Faster add-ons landing next
week-ish and b) Hello implemented as an add-on, we can start building
week-ish and b) Hello implemented as an add-on, we can start building
and shipping Hello on the regular trains that way. This would be
and shipping Hello on the regular trains that way. This would be
Line 34: Line 43:
is a way to stage the approach.
is a way to stage the approach.


2. During q3, we build some kind of protoype CI pipeline for shipping
** During q3, we build some kind of protoype CI pipeline for shipping
Hello more frequently. Take an experimental approach.
Hello more frequently. Take an experimental approach.
We don't need to get it working for all channels, or all OSes, or
We don't need to get it working for all channels, or all OSes, or

Latest revision as of 20:21, 1 September 2015

September 1, 2015

Meeting details

Attendees

  • Larissa
  • Not Laura today, apologies.

Agenda

Discuss Q3 goal updates per team:

  • Client integration (Mossop/rhelmer)
** patch for loading system addons is in Rob's queue to review now 
** following that is work to request new system addons
** hello is now working as a prototype addon
** https://bugzilla.mozilla.org/show_bug.cgi?id=1186172#c7
  • Build pipeline (mrrrgn out, JP present)
** JP getting reacquainted, learning task cluster.  
  • Test automation (mbrandt or jgriffin)
** still on hold
  • QA (krupa)
** Krupa out but her QA plan will hit the wiki this week
  • IdeaTown (nchapman/jgruen/edwong)
**   
  • Updates (tarek)
**
  • Fat Fennec (richard)
**
  • l10n (axel)
**

Roundtable and Q&A

  • Release Pipeline next steps - Laura's proposal from the list:
    • Since we have a) Client support for Go-Faster add-ons landing next

week-ish and b) Hello implemented as an add-on, we can start building and shipping Hello on the regular trains that way. This would be almost exactly how we treat pdf.js and Shumway. This way we have a system add-on, but we're not shipping it any faster than usual, and can rely on the normal build, test, l10n, and update mechanisms. This is a way to stage the approach.

    • During q3, we build some kind of protoype CI pipeline for shipping

Hello more frequently. Take an experimental approach. We don't need to get it working for all channels, or all OSes, or shipped to end users. We try using taskcluster and just doing builds for Linux, as a starting point, since that's probably the easiest.

  • Shipping Hello as an addon in trains - which pieces need to go in which trains?
  • Other topics?


Actions:

Administrivia: