Thanks, David. I’ve updated the Callisto
project site  with the newly revised process.
Also, note that the PMC requested a “bit
freeze” deadline of 6/14 to enable cooldown in advance of the
Callisto-wide bit freeze. That means that only 3 weeks remain for 1.5 work.
During the 5/31 – 6/14 phase of PMC
approval, we’ll add new calls (as frequently as daily if required) to
ensure that defects are not stalled on PMC approval during the endgame and to
provide component leads with an interactive forum for discussing them. If there
are no pending defects in the queue or they are receiving rapid PMC votes, then
we’ll continue with the former approach of asynchronous/offline approval.
From: David M Williams
Sent: Tuesday, May 23, 2006 4:30
Cc: Tim Wagner
Subject: triage, fix, and approval
process for one week, and remainder of 1.5
Tim Wagner is/will be sending out a more official
process as this was discussed and decided at today's PMC meeting, but, I think
he had to get on a plane before he could type them up,
here's a semi-official version for the remainder of this week. We will, btw,
also re-discuss the process for the remaining 1.5 time at Thursday's status
call. I'm just sending this out now,
we haven't communicated this yet and some folks appear to be waiting for
approval (as they should, under the old rules)
so, please keep posting "bugs being fixed" to mailing list ... but no
need to wait to release to build (until 31st, that is).
(RC4) – component lead check-in approval and “post hoc” PMC
means component lead can approve for release and build, but lists of defects
for which fixes provided should
be published to wtp-dev list. This is partially to make it easier for PMC
"post hoc" review (and PMC members make
with component leads if something seems inappropriate) and its also to help
keep adopters and other Callisto projects
of changes that could theoretically affect them.
for the following two weeks, I think it was, we'll go back to fuller PMC
approval, but with some ideas to ensure doesn't
down important fixes.
suggest component leads continue to triage bugs well so some idea of proposed
defects to address in 1.5 is well understood.
we do not have much room to "slip dates" due to Callisto agreements,
so it will be better to have a
understood list of limitations or bugs, rather than try to fix tons of stuff
right up to the last minute, which could result in
regressions that are worse than the bugs to be addressed.