I wasn’t able to attend the PC this
week due to a conflict.
Re the release train topic in the proposed
agenda - Choo choo…
Re TPTP alignment with the release train,
I have action to formally indicate the TPTP will board the train – please
consider that done.
Our specific plans to date (based on what
we currently know) are as follows:
|
What
|
When
|
Why
|
|
EP 3.2
M2
|
Sept
23
|
|
|
TPTP 4.1 I2 Candidate (Test Build on EP 3.2
M2)
|
Oct 17
|
Build of current TPTP 4.1 functionality
in preparation for first formal build on EP 3.2 Nov 18
|
|
TPTP 4.1 GA (Available on EP 3.1.1)
|
Nov 11
|
Next major TPTP release
|
|
|
|
|
|
EP 3.2
M3
|
Nov 4
|
|
|
TPTP 4.2 “M3” (Available on
EP 3.2 M3)
|
Nov 18
|
First formal TPTP build on EP 3.2
(Functionally equivalent to TPTP 4.1 GA)
|
|
EP 3.2
M4
|
Dec 16
|
|
|
TPTP 4.2 “M3” (Available on
EP 3.2 M3)
|
~Dec 17
|
Second formal TPTP build on EP 3.2
(Functionally equivalent to TPTP 4.1 GA)
|
|
TPTP 4.2 Formal start of development
|
Jan 9
|
We have “down-time” between
Nov 11-Jan 6
|
|
EP 3.2
RC0
|
Apr 1
|
|
|
TPTP 4.2 I2 (Available on EP 3.2 RC0)
|
Apr 14
|
We’ll plan alignment with EP
milestones during this period when such are published
|
|
TPTP 4.2 I3 (Available on EP 3.2 RC?)
|
Jun 2
|
Final TPTP feature development iteration
to be aligned as appropriate with EP milestones during this period when
published.
|
|
TPTP 4.2 GA (Available on EP 3.2 GA &
EMF GA)
|
~Jun 30
|
We’ll plan alignment with EP
milestones during this period when such are published – we’re
generally expecting to be in frequent build/test mode toward ~simultaneous
closure with EP
|
From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx]
On Behalf Of Bjorn Freeman-Benson
Sent: Tuesday, September 20, 2005
7:01 AM
To: eclipse.org-planning-council
Subject: [eclipse.org-planning-council]
September 20 Confernce call agenda
613.287.8000
or 866.362.7064
passcode 874551#
8am PDT, 11am EDT, 5pm CET
Actually, I don't have much of an agenda for today's first resumed monthly
conference call so it might be very short.
- We could discuss the conference call timing,
although that might be difficult because the people most interested in
changing the time are those that cannot make today's call :-)
- I'd also like to hear from BIRT, DTP, TPTP, WTP,
and the Tools projects about the status of sync'ing their project plan
with the release train project plan.
- And a reminder that everyone is going to freshen
their web content (at the very least, remove / annotate dead information)
by the end of the month.
--
