[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cross-project-issues-dev] platform RC1a will be contributed tocallisto RC1
|
Another clarification :-)
Platform RC1 is NOT currently in the
callisto staging area. The platform jars that are there are from
3.2M6. I didn't update the area with the content from RC1 because
in an earlier note David stated to wait until Wednesday to start staging
for RC1. Wednesday was also the day we found out we would be spinning RC1a.
I'll put RC1a in the staging area once
it is promoted.
Both WTP and Platform-UA have signed
off on I20060419-1640 build for RC1a.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=135107
http://download.eclipse.org/eclipse/downloads/drops/I20060419-1640/index.php
The build will not be promoted until
the performance tests complete. If you are looking for RC1a, this
is it. The promote tool just renames all the zips.
Kim
John Arthorne/Ottawa/IBM@IBMCA
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
04/20/2006 01:49 PM
|
Please respond to
Cross project issues |
|
|
To
| Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| 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.
"Thessin, Tyler"
<tyler.thessin@xxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
20/04/2006 12:13 PM
|
Please respond to
Cross project issues |
|
|
To
| "Cross project
issues" <cross-project-issues-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [cross-project-issues-dev]
platform RC1a will be contributed tocallisto
RC1 |
|
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 Apr 14)?
RC1 (14-Apr .. 21-Apr)
Starting with RC1, each project
will apply its own ramp-down rules.
·
14-Apr - Platform
·
19-Apr - CDT, DTP, EMF, GEF,
VE
·
21-Apr - BIRT, GMF, TPTP, WTP
Thanks,
--tyler
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx]
On Behalf Of Kim Moir
Sent: Thursday, April 20, 2006 7:30 AM
To: Cross project issues
Subject: [cross-project-issues-dev] platform RC1a will be contributed
tocallisto RC1
Just a FYI, the platform ran another build toward RC1a for the following
issue identified by the WTP team.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=135107
http://dev.eclipse.org/mhonarc/lists/platform-releng-dev/msg06480.html
Therefore, we will not be be contributing platform RC1 to callisto, but
platform RC1a
Kim_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
