CloudServices/Meetings/2010-05-18

From MozillaWiki
Jump to: navigation, search

Agenda:

  • Release schedule (need to revise)
    • Code freeze (for blockers): Apr 30 (Delayed, new date: May 4)
    • Registration server code complete: Apr 30 (Done)
    • String Freeze: Apr 30 (Delayed, new date: May 4)
    • H/W set up complete and configured: May 5
    • Load testing done : May 13 (Delayed, new date: May 14)
    • l10n complete: May 11
    • Security reviews done: May 10
    • RC release date: May 12
    • QA release sign off: May 13
    • Unit tests for Primary done: May 10
    • Web content finalized and staged: May 13
    • PR/Announcement complete and finalized: May 13
    • GA date: May 17, 2010
  • 1.3 release status update
    • Production environment
    • Load tests
    • Client
    • QA
      • Client
        • Unfixed bugs filed since b5 release. None appear to be stop ship bugs.
        • Bugs fixed since b5 release. They will need verification in b6.
        • ddahl created JetCrawl, which builds bookmarks and history off of topsites. Works with older jetpack sdks. Update: filed bug 566707 to track changes.
      • Load
        • utest test completed 1st baseline measurements. Waiting for green light to repeat tests under load.
      • Automation
        • Dynamic account creation is working fine using staging server
        • Need about 10 more days to finish with client, then will work on results reporting to MySQL db
        • Will work on docs this week, so that when ashah starts writing tests next week he'll have some info to start with
    • Metrics
    • Marketing
    • Support
    • iPhone client
  • Discussion Items
    • Load test...
    • utest status?
    • We need to test migration ?
    • Large profiles - tchung will look into alternatives.
    • Metrics is going to write a collector script and will switch over when we go live.
    • AI: MConnor and I will talk about what else needs to be localized.
    • AI: Need a blog post draft by the end of this week.
    • Ops Runbook needs to be done.
    • AI: Logging needs to be set up in production for security.
    • SLA: onsite backup every 2 days, offsite backup every week.
    • AI: Ragavan will talk Mayumi/WebDev about changing/localizing the updated page.