Confirmed users
385
edits
Services/Meetings/RapidRelease/2012-04-20: Difference between revisions
Services/Meetings/RapidRelease/2012-04-20 (view source)
Revision as of 21:40, 20 April 2012
, 20 April 2012→Notes from the meeting
Rsoderberg (talk | contribs) |
|||
| (26 intermediate revisions by 3 users not shown) | |||
| Line 5: | Line 5: | ||
= Clientside = | = Clientside = | ||
== Desktop == | == Desktop == | ||
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=2911739;classification=Client%20Software;chfieldto=Now;query_format=advanced;chfieldfrom=2012-03-02;bug_status=RESOLVED;bug_status=VERIFIED;bug_status=CLOSED;component=Firefox%20Sync%3A%20Backend;component=Firefox%20Sync%3A%20UI;product=Mozilla%20Services, bugs closed since rapid release] | |||
=== Firefox 12 (going to release: 2012-04-24) === | === Firefox 12 (going to release: 2012-04-24) === | ||
* minor | |||
=== Firefox 13 (going to beta, release: 2012-06-05) === | === Firefox 13 (going to beta, release: 2012-06-05) === | ||
* minor | |||
=== Firefox 14 (going to aurora, release: 2012-07-17) === | === Firefox 14 (going to aurora, release: 2012-07-17) === | ||
* minor | |||
=== Firefox 15+ === | |||
* sync 2.0/browser id integration | |||
* contacts sync | |||
== Mobile, Android Native == | == Mobile, Android Native == | ||
=== Firefox beta === | === Firefox beta === | ||
* will be cut from aurora once the beta blocker list drops to 0 | |||
* may spend more than 6 weeks baking on beta | |||
=== Firefox aurora === | === Firefox aurora === | ||
* will follow the 14 train, hopefully | |||
=== Life after the 1.0 === | |||
* https://wiki.mozilla.org/Services/PushTabToDevice | |||
* Feature parity | |||
* Sync 2.0 and Persona integration, presumably. | |||
== B2G == | |||
* Sync 1.1 or Sync 2.0? | |||
** Resilient Sync is only available for Sync 2.0 | |||
* Launch date to release channel? | |||
** Operations coordination required for launch capacity | |||
= Serverside = | = Serverside = | ||
| Line 17: | Line 38: | ||
* On target for launch next week | * On target for launch next week | ||
* tokenserver is currently performing 500qps on the stage machine | * tokenserver is currently performing 500qps on the stage machine | ||
* See also "Upcoming Projects: HSM" below | |||
== Sync 2.0 == | |||
* Sync 2.0 support is not targeted for any Firefox release? | |||
* Coming along nicely. | |||
** Tokenserver is launching with aitc. | |||
** Storage server is having final tweaks done (since most of them are being done for aitc, too). | |||
** Eng could theoretically ship with any reasonable lead time | |||
** Ops and _____ to agree on launch date for Sync 2.0 | |||
* Open issues over flag day. | |||
== Sync 1.1 == | |||
* Build issues preventing deployment of existing code | |||
* Small bug fixes queued for several components (storage, auth, etc) | |||
* How is Sync capacity doing? | |||
== Resilient Sync == | |||
* What is the plan currently for durable storage? | |||
* What is the plan for B2G partners? | |||
== Upcoming Projects == | |||
=== Hardware Security Module === | === Hardware Security Module === | ||
| Line 23: | Line 67: | ||
* Dev server VM is finally up, but rtilder still has no account on it | * Dev server VM is finally up, but rtilder still has no account on it | ||
* Actual HSM is going to live in MV cage for now | * Actual HSM is going to live in MV cage for now | ||
= Roadmap, Feature Pitches = | = Roadmap, Feature Pitches = | ||
| Line 36: | Line 73: | ||
= Notes from the meeting = | = Notes from the meeting = | ||
* Ops needs to do capacity testing for b2g | |||
** and with real devices | |||
** what the per device impact is | |||
*** maximum # of devices (needs to know in jul/aug timeframe) | |||
* date & plan for 2.0 still up in the air | |||
* https://github.com/mozilla/browserid/wiki/Scaling-to-1M | |||
* scl3 has been pushed back | |||
* budget has not been finalized for capacity | |||
* hoping to make a call on implementation of contacts for b2g next week | |||
* discussion of cleartext data, and whether reconciliation of contacts should be client or server-side | |||
** considering standardizing as much of this as possible in the client | |||