RE: [cross-project-issues-dev] platform RC1a will be contributed tocallisto RC1
Just to clarify, the platform RC1 was
available on April 14th and is in the staging directory (http://download.eclipse.org/callisto/staging/).
Because of the problem with interaction with WTP, the RC1a build
is being created, but it only contains a single fix for that one problem.
I.e., you can continue to use platform RC1 to build and test against, and
RC1a can be swapped in to replace RC1 when it's available. In this
particular case I wouldn't expect much impact downstream.
What’s our agreed to policy
regarding Callisto dates and slips of early dependencies. E.g., Callisto
RC1 states the three categories of deliveries as absolute dates. But,
how can the +1 and +2 categories deliver on the absolute date if the earlier
dependency is not available on time.
In this specific case, what
is the expected impact to the Callisto RC1 schedule related to Eclipse
Platform delivering RC1a as their Callisto RC1 contribution (later than
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
20/04/2006 12:13 PM
Please respond to
Cross project issues
|"Cross project issues"
platform RC1a will be contributed tocallisto
RC1 (14-Apr .. 21-Apr)
Starting with RC1, each project
will apply its own ramp-down rules.
- CDT, DTP, EMF, GEF, VE
- BIRT, GMF, TPTP, WTP
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Kim
Sent: Thursday, April 20, 2006 7:30 AM
To: Cross project issues
Subject: [cross-project-issues-dev] platform RC1a will be contributed
Just a FYI, the platform ran another build toward RC1a for the following
issue identified by the WTP team.
Therefore, we will not be be contributing platform RC1 to callisto, but
cross-project-issues-dev mailing list