I see: 12-Apr 9am PT/noon ET
- CallistoRC1 status
No?
From:
eclipse.org-planning-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of Tim Wagner
Sent: Wednesday, April 12, 2006
11:24 AM
To: eclipse.org-planning-council
Subject: RE:
[eclipse.org-planning-council] Callisto RC1 conference call 12-Apr(today)
Did I get the day/time
wrong? It’s 8:15am PDT on April 12th, which is what it says on
http://www.eclipse.org/projects/callisto.php,
but I don’t hear anyone else on the call.
In lieu of a call, my
answers via email:
- RC0 status from each
project. WTP is on track.
Some bugs have been noted in our validators, but that won’t preclude
us being ready and testable as part of Callisto.
- Update Site. Yes, and my understanding is that we are using the staging site as
intended.
- RC1. Yes and no; yes in the sense that WTP doesn’t have a separate
RC1 production/rampdown timeframe; no in the sense that we cannot pick up
the RC1 release from the platform the same day it is produced, and will
have to absorb it later, in preparation for RC2. That’s probably a
flaw in our Callisto RC planning.
- RC2 status from each
project. This is an excellent
question. W.r.t. rampdown policies, WTP is shifting into bug fix/rampdown
mode (no new features, no major implementation changes, focus on bug
fixing, etc.) on 4/28. However, we do need internal alignment with the
platform or risk being “one off” as we are for RC0/RC1 right
now. Can the platform rampdown a few days early?
- Ramp Down Policy
from each project. See http://www.eclipse.org/projects/callisto.php
for WTP’s policies.
- Bug Contest. WTP has received only one entry to date, and the WTP PMC voted to
declare it “good” and I emailed it to Ward & Bjorn
yesterday. As to why more people aren’t participating…I
suspect that on the project teams, everyone is at/above 100% working on
their “own stuff” and have no additional bandwidth, and
outside the project teams the contest/Callisto/milestone releases are not
well enough known. Perhaps a link on the download site for the Eclipse
Project itself to the bug contest to catch folks who normally download
milestone from there and don’t know about Callisto? I’ve
advertised inside my company (not to much effect) FWIW.
Finally, a word on
testing in the context of Callisto: Sadly, not much progress to report, other
than some anecdotal work by a few people who’ve tried it. I’m
hoping that once we get to the rampdown we can institute the approach for WTP
that we talked about on these calls: alternating (by person or time period)
between testing WTP standalone vs in the context of Callisto. This remains the
single biggest risk factor in my mind, and changing behavior/culture to include
the idea of testing within the context of a new release vehicle is proving to
be a challenge.
From:
eclipse.org-planning-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of Bjorn Freeman-Benson
Sent: Tuesday, April 11, 2006
11:53 PM
To: eclipse.org-planning-council@xxxxxxxxxxx
Subject:
[eclipse.org-planning-council] Callisto RC1 conference call 12-Apr(today)
613.287.8000
-or- 866.362.7064
passcode 874551#
(Ward will be hosting the call as Bjorn is
traveling.)
- RC0 status from each
project. According to our
schedule Platform, CDT, DTP, EMF, GEF, and VE have completed their RC0 and
BIRT, GMF, TPTP, and WTP should complete their RC0 this Friday. What is
the status of these RC0s? Will we have a final Callisto RC0 on Friday?
- Update Site. Will we have an RC0 update site on Friday? Are all the projects
sending their update site information to David? How are we handling the
"RC0 is in the midst of being released one step at a time while M5 is
the milestone on the update site" - are we using our staging update
site?
- RC1. According to our schedule, RC1 is also this Friday. Thus the RC0
and RC1 are, for everyone except the Platform, the same event. Does
everyone agree?
- RC2 status from each
project. According to our
schedule, RC2 is in two and a half weeks. What ramp down policies are the
projects applying for RC2? How many days delay is each project using for
RC2? When will the Platform go to RC2? After that, when will CDT, DTP,
..., etc have their RC2s? And when will BIRT, GMF, TPTP, and WTP have
their RC2s? Will this all happen by 28-April?
- Ramp Down Policy
from each project. What ramp down
policy is each project applying? How many sign-offs are required to
release a change? What notifications are sent for each change and to whom?
Etc.
- Bug Contest. The bug contest has very few (I think two legitimate) entrants.
Does anybody have an idea why? Bugs but no good ones? No bugs being
entered?
We're coming into the end game now which means that
we need to ramp up communication and coordination. I think the goal for this
call should be to come away with a concrete plan from each project for the end
games and the coordination and the tightening build schedule and to make sure
that we have the update site working.
|
