Services/Meetings/RapidRelease/2012-04-20: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 25: Line 25:


* Sync 1.1 or Sync 2.0?
* Sync 1.1 or Sync 2.0?
* Launch date for Operational capacity planning?


= Serverside =
= Serverside =

Revision as of 17:28, 20 April 2012

Purpose & Audience

  • Ops, QA, Engineering, Management, Product, Product Marketing, Support. If you have a stake in Sync, someone from your group is expected to be present.
  • last meeting

Clientside

Desktop

Firefox 12 (going to release: 2012-04-24)

Firefox 13 (going to beta, release: 2012-06-05)

Firefox 14 (going to aurora, release: 2012-07-17)

Firefox 15+

  • sync 2.0/browser id integration
  • contacts sync

Mobile, Android Native

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

  • will follow the 14 train, hopefully

Life after the 1.0

B2G

  • Sync 1.1 or Sync 2.0?
  • Launch date for Operational capacity planning?

Serverside

AITC

  • On target for launch next week
  • 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

  • Targeted for AITC initially, may be used by other products someday
  • At risk due to hardware confusion. Corey and Jeremy are looking into what is needed and where to put it in the marketplace hardware allocation
  • 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

Roadmap, Feature Pitches

  • Sync has no official roadmap at this time, but k9o priorities are generally known
  • Dropbox has expressed interest in Sync consuming their developer APIs

Notes from the meeting

Retrieved from "https://wiki.allizom.org/index.php?title=Services/Meetings/RapidRelease/2012-04-20&oldid=422581"