Well .. while we are all being so agreeable
.. it might help too if the schedule presentation emphasized the end-date,
instead of the range .. I think that adds to the confusion too.
Such as
RC1 (14-Apr .. 21-Apr)
14-Apr - Platform
19-Apr - CDT, DTP, EMF, GEF, VE
21-Apr - BIRT, GMF, TPTP, WTP
RC2
(28-Apr .. 5-May)
28-Apr - Platform
3-May - CDT, DTP, EMF, GEF, VE
5-May - BIRT, GMF, TPTP, WTP
RC3
(12-May .. 19-May)
12-May - Platform
17-May - CDT, DTP, EMF, GEF, VE
19-May - BIRT, GMF, TPTP, WTP
to
RC1 (21-Apr)
14-Apr - Platform
19-Apr - CDT, DTP, EMF, GEF, VE
21-Apr - BIRT, GMF, TPTP, WTP
RC2
(5-May)
28-Apr - Platform
3-May - CDT, DTP, EMF, GEF, VE
5-May - BIRT, GMF, TPTP, WTP
RC3
(19-May)
12-May - Platform
17-May - CDT, DTP, EMF, GEF, VE
19-May - BIRT, GMF, TPTP, WTP
Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
04/20/2006 12:03 PM
Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
+1 I agree.
Callisto is a release train that is
supposed to showcase all the projects releasing together, so it would be
best if we highlighted the Callisto release, instead of the releases for
individual projects. It's too confusing. _______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev