Chandler Engineering Meeting, Thursday February 8th 2007

Present: Katie, Heikki, Sheila, Aparna, Philippe

Agenda

• 0.7alpha5 Progress : What happened this week. Progress, blocking issues.
• 0.7alpha5 Schedule: Let's review the plan as outlined last week.
• Cosmo Integration: Should we have a special flag (keyword?) for those bugs that are interop bugs? (hard to know when logging them if they are Chandler or Cosmo bugs...)
• QA: Aparna's update
• Other
  • Win2K: got some bug reports from users. How do we handle those without adding a new OS to the list of supported OSes?

0.7alpha5 Progress

• Email landing
• AutoTriage: need to be refined for alpha5
• EIM: Jeffrey and Morgen and PJE working on this

0.7alpha5 Schedule

• We need to explain what the various milestones mean. Here's a short explanation:
  • Feature Freeze: 3/6: All "task" fixed or moved to Future (cut from the release), code committed and ready to be tested by QA. Criteria: if there are "task" open in Bugzilla and that those "task" can't be pushed out of Preview, the milestone is not reached and the schedule needs to be adjusted
    • After Feature Freeze, feature work needs to be approved by bug council and should be motivated by being required for Preview to be usable. Performance work including potentially architecture change can still happen.
  • Code Complete: 3/28: All code in, architecture and feature tweak completed, perf work completed. Criteria: if the perf targets are not met or some feature need to be tweaked deeper, the milestone needs to be pushed
    • After Code Complete, only bug fix work and stabilization can be done. Bugs must be approved by Big Council. Code changes need peer review before commit.
  • Code Freeze or ZBB (Zero Bug Bounce): 4/19: All bugs fixed. Criteria: if there's more than 10 blocking bugs outstanding, the milestone is not reached.
    • After Code Freeze, only "recall class bugs" and blockers can be fixed. Bugs are triaged daily, code changes need to be peer reviewed before commit.
• Release: 4/24

Cosmo Integration

• Let's use the interop keyword though it's used for all kind of interop issues

QA

• Cosmo 0.6 migrationg testing under way
• Testing new feature on Chandler

Other

• Win2K and other OSes: we can't commit on all OSes (not enough TBoxes, etc...). We should mark those bugs helpus and accept patch.
• Performance: we need a more representative data set. Heikki is taking this action item.
• Make this meeting biweekly: let's talk about engineering things (machines, build, etc...) and reserve the progress discussion for the weekly Monday morning "Preview Countdown" meeting.

-- PhilippeBossut - 08 Feb 2007