Schedule

The intent is to "line up" our 3.2 milestones with first four milestones of Helios Release. Our 3.2 work will also be input to any Helios builds.

M1 8/14

M1 8/21

WTP 3.2 Plans Due 8/14

M2 9/25

M2 10/2

Initial WTP 3.3 plans due 10/2 -- for Helios!

M3 11/05

After M3, start 3.2 Rampdown and PMC Review

M3 11/13 Start 3.2 Rampdown and PMC Review

M4 and 3.2 Release Build 12/10

M4/Release 12/18

WTP 3.3

We now have once-a-day Helios builds. Same WTP code. Different pre-req Platform. The goal is to make sure our 3.2 stream is at least compatible with both Galileo and Helios. Or, if we can not literally achieve being compatible, we should document why not and at least understand it.

Any issues?

Other business

It was asked if bugs have been open for all retrospective action items yet (answer: no) as there is still concern about builds taking so long (there are bugs to improve builds).

There will be a new "Community Forums" front end to newsgroups. It will be even more important to make sure descriptions for our WTP groups are clear, even for the "casual user".