[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [wtp-dev] PMC decision on project and server API enhancements
|
So it
sounds like 1.1 is the real 1.0 (as 1.0 was originally
defined).
What/who is really driving the July release
date? Sorry to ask such a pointed question, but it seems like we are
incurring a considerable amount of overhead (rampdown, docs, branching
1.1, migration utilities, etc.) by sticking to an official July
release.
-Ted
Ted,
WTP
1.1 is on Eclipse 3.1, around 12/15. The focus is on promotion of provisional
APIs. New function will go into WTP 2.0 on Eclipse 3.2, 2Q06.
Arthur Ryman,
Rational Desktop Tools
Development
phone: +1-905-413-3077, TL 969-3077
assistant:
+1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile:
+1-416-939-5063, text: 4169395063@xxxxxxx
intranet:
http://labweb.torolab.ibm.com/DRY6/
"Ted Bashor"
<tbashor@xxxxxxx>
Sent
by: wtp-dev-bounces@xxxxxxxxxxx
05/18/2005 04:35 PM
|
Please respond
to
"General discussion of project-wide or architectural
issues." |
|
|
To
| "General discussion of
project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [wtp-dev] PMC
decision on project and server API
enhancements |
|
Could we have some more details on the roadmap the PMC has
in mind?
Is the idea that 1.1 will be based on Eclipse 3.1 or 3.2? A
second release of WTP this year on top of 3.1 might offer improved
provisional api and bug fixes, but seems unlikely to contain significantly
more "non-provisional" API, given anticipated 3.2 changes.
-Ted
-----Original Message-----
From:
wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]On Behalf
Of Tim Wagner
Sent: Tuesday, May 17, 2005 11:12 AM
To:
wtp-dev@xxxxxxxxxxx
Subject: [wtp-dev] PMC decision on project and
server API enhancements
Because of the need to ship in a timely manner, the WTP PMC has decided
to postpone the suggested enhancements to the flexible project model/server
APIs. Although these are important pieces of the WTP framework, scheduling
constraints and incipient change in this area in the platform itself have
caused us to defer those changes until the 1.1 release. The PMC resolved
to
- Maintain the current shipping
schedule
- Make the quality of user tools the
focus of the 1.0 release
- Make the framework (APIs) the
focus of the 1.1 release, including finalizing the project and server
models
One natural fallout of this decision is that
the server and project APIs must be provisional in 1.0, given that they are
almost certain to change for the reasons cited. WTP will document them as such
(JavaDoc, component.xml, release documentation) but is not currently planning
on altering the packaging because of the delays involved and the shortness of
the remaining schedule._______________________________________________
wtp-dev mailing
list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
