Here's an outline of the 0.2 plan. The goal is to get everyone on the same page as to where things stand and what needs to be done to get 0.2 out of the door.

1. We have a high-level set of candidates for the 0.2 release as sketched out in my spreadsheet. Several of these candidates highlight the need for more detailed architectural plans before we can move forward (i.e. snakes).
2. We had a week long series of process and architectural discussions to kill the "snakes" we've identified in IssueSummaryTableOfContents. Topics include qa, dev process, database, and security. There are other issues identified which won't be discussed this week. These will have assigned owners and the process to resolve these issues will be as discussed in the "dev process" meeting (see DevelopmentProcessIssueSummary).
3. From our discussion last week, we assigned owners of the candidates listed in (1). We hope to break these candidate features into fine-grained tasks highlighting best-guess estimates and tasks dependencies, as we did for the 0.1 release. We want to complete this by end of this month 5/30 (which is this Friday). The exact way in which we enter and turn the tasks into a schedule (e.g. use Bugzilla like we did in 0.1) will be detailed by Michael.
4. From (3), we will develop a detailed plan and schedule for 0.2. We will prioritize and defer tasks and juggle dependencies in order to ship 0.2 around the September timeframe. At this point, it is more important that we ensure key goals for the 0.2 release are met (e.g. goal to demonstrate end-to-end data handling) than to meet the September timeframe. Once we have a concrete plan in place, then it is important to shoot for an agreed upon set of deadlines.
5. All 0.2 and subsequent tasks will be organized into a set of long-standing projects. The list of projects and their accompanying project pages will be chosen and published shortly.
6. As always, we will monitor progress and adjust/re-prioritize tasks accordingly.
7. A high-level set of goals and purposes for 0.2 can be found at ZeroPointTwoPlanning

-- ChaoLam - 27 May 2003