Preview Meeting July 30, 2007

Agenda

• Server (Ted)
• Desktop (Philippe)
• Service (Jared)
• QA (Aparna)
• Non-code deliverables (Katie)
• OSCON follow up? (Katie)

Notes

Server

• recurrence related bugs need to get fixed, Matt is in process of swagging
• Code complete definition for server: zero bugs for release candidate
• 39 bugs right now -- re-examine to see if they should block the release
• Most important thing: make sure QA not blocked
• Rebranding, release announcements -- should not be counted against total for code complete
• Bobby is looking at performance
• Ted waiting for the swags to come in before giving schedule update
• Next step: Pass through the p2s/p3s? tomorrow afternoon
• week after code complete for release
• Daily QA sessions, bug council every other day

Desktop

• Supposed to hit ZBR today, have 45 bugs, not 39
• Most people at 3/4 bugs: 5 day estimate (need to sync up with Stearns after oscon)
• Sharing bugs still coming in, these are usually high priority. They are usually found doing roundtrip testing using data that has been accumulated over time. Edits from multiple people, different shares.
• Fragile area: EIM, recurring events and triage
• Next actions: Swags for new bugs, deadlines, particpate in testing sessions
• Question on list: Release notes? Where are they linked from?

QA

• Testing schedule this week? Next action: send out schedule for week.
• Last week, didn't have a very good integration test spec. Collected scenarios with PPD team. Aparna put it down in spec: PreviewIntegrationTestSpec
• Expect a peak soon in new bugs, then start to fall. No new areas after today/tomorrow, will have covered all areas.

Service

• TOS? Privacy Policy? Meeting with lawyer scheduled Thursday afternoon.
  • TODO: translating to HTML, too long for what it is saying, integrating into cosmo UI
• Next actions: Jared meeting with lawyer, Jared following up in bug
• Branding related bugs: NOW is the time to get those bugs done
  • Final Copy Review -- Mimi is waiting for conflicts to be resolved -- ask Travis to help
  • list of things that can get better for hub, not on shortlist. outgoing email: Jared will open a bug to review Hub branding changes
• Confident in hardware now
• Benchmarking is now the issue
• Bear offered help with hub related gruntwork
• Feedback service is blocking QA, perhaps Bear can help
• Jared worked on Run Book last week, should have full first draft by end of week. Next step to send out draft. One of the most important things is to agree on what is in the Run Book. Run Book is in subversion. Bear and Randy to review.

Non-code deliverables

• Blog post interop -- Katie needs to follow up on this
• Feature list, release notes, known issues
  • Ted to do his part.
• Screencasts are necessary, Katie will own putting one together
• Pieter started working on the user guide, we've signed the contract

OSCON

• Put information from Ted/Mimi talk into a paper, blog?
• Materials/artifacts from Windmill talk made more clearly available?
• Blog updates from attendees?