Preview Meeting July 23rd 2007

Agenda

• Cosmo status (Bobby)
• Desktop status (Philippe)
• OSCON (Katie)
• Documentation and wiki update (Mimi, Katie and Jared)

Notes

Cosmo status

• A cluster of bugs are related to stale data/caching issues (bugs are marked as [possibleCaching] in status whiteboard). Travis has a band-aid fix, the cosmo team would like to test that out in the next testing sessions.
• Getting in enough testing (in particular round trip testing) is a risk, so the Cosmo team is trying to have test sessions every day. They're alternating between qa/ppd focus sessions and group collaborative sessions. After test sessions, the team will scan for P1s, so that developers have up to date priority lists.
• We'll run a QA session at OSCON.

Desktop status

• Declared Code Complete last week
• Commit restrictions in place (reviews, bug reference), 3 Bug Council per week
• Bug count low (58 bugs, average of 5 bugs per dev) but we lost one dev (Grant) and 2 at OSCON this week (Bryan, Robin). Will be hard to hit ZBR by next week. That's the biggest uncertainty right now.
• Philippe focusing on Release Management duties and handling Grant's duties as well
• Aparna noted that the QA team is primarily focused on Cosmo, so desktop is getting less testing mileage. How you can help: validate recently closed bugs.

OSCON

• Demo script (Katie): Are we ready? Are there critical bugs we need to worry about for the demos?
  • Katie will send this out
• Business cards (Mimi): Where are we with that?
  • Cards should be at Ted's hotel. Katie will bring cards back to office.
• Landing page (Mimi): Look like it's done (Bug#9556 marked FIXED). Anything pending?
  • Mostly done, with two important MUST HAVEs: Change release date (Jared), Update downloads page with text to reflect current status as of OSCON.
• People at OSCON should point people at chandlerproject.org for downloads and login. We'll use this to track metrics. People at OSCON should be encouraging others to try it out, setting just-before-preview expectations.
• qacosmo remains a testing/try-it-out resource during the course of the conference. QA will be updating the site regularly without wiping the data (unless something goes wrong and they need to). We considered setting up a separate demo/dogfood instance, but have not done so for lack of time.

Documentation and wiki update

• Wiki update (Katie, Jared, Mimi)
• Review pending actions from last week
  • Chandler Desktop release notes and known issues (Philippe and Jared) - No progress on this last week. Need to happen this week.
    • Mimi is taking known issues for both Desktop and Server, but will need input from Philippe and Ted.
  • Redirectsfor OSCON (Jared) - Done? done
  • Landing page to look right in IE7 (Mimi) - Done? done

Code Related Deliverables

• Philippe checked and updated the wiki tables
  • Desktop is done
  • Cosmo is all done except for 2 bugs (Bug#8622 and Bug#8642)
  • Hub is not done (only one Bug#8643 logged). Is there another list somewhere? Is it combined with all the other stuff that Jared is traking off the OSAF Bugzilla?

Non Code Related Deliverables

• aka Product Side Documentation
• Philippe checked and updated the wiki tables
• Looks like we're not driving very hard on those (block the launch but not the release). Most are assigned to Pieter. (Katie) Update?
  • Actually, we've been driving very hard on these, and the wiki/web is in pretty good shape. All Pieter's bugs were reassigned several weeks back, he is only responsible for the user guide, which he is starting on this week. Mimi, Jared, Ted have made significant edits and wiki/website are looking pretty good. The big gaps are feature list and known issues, which Mimi is on top of. Jared has a long task list, he probably won't get all of his wiki/web tweaks done. If it must be done by preview, be sure to prioritize it as P1.

Other

• Update of qasharing to Cosmo 0.7 to happen today (Jared, Bear). Are we OK? Yes
• Term of Service (Jared). Update?
  • Jared sending feedback on TOS to lawyer for 2nd round. Needs to repeat process for Privacy Policy.