RE: [wtp-dev] PMC decision on project and server API enhancements

[Arthur Ryman <ryman@xxxxxxxxxx>]

Ted,

Great question.

The Eclipse process for creating platform
APIs requires that we have confidence that they satisfy consumer requirements.
M5 was planned as the period of time where we gathered feedback. In light
of the feedback provided by you, we have come to the conclusion that portions
of the proposed API require further development, and so we are now classifying
them as provisional. This gives us an opportunity to design an API that
we are all comfortable with during the 1.1 timeframe. This is exactly how
the process should work.

Another important element of the Eclipse
development process is to ship useful, stable code at regular intervals.
We are aligning WTP 1.0 with Eclipse 3.1. Our goal is to ship as closely
as possible with Eclipse platform releases. The way to achieve the schedule
is to defer function. There will always be more function that we'd like
to include than we can contain in the schedule. We must therefore defer
function if possible. The only circumstance under which I would support
delaying our release date is when some "defining" function was
not ready. For example, if we say that the major theme of WTP 2.0 is to
support J2EE 1.5, then we should not ship WTP 2.0 until the core J2EE 1.5
development use cases work.

The goal of WTP 1.0 is to provide a
core set of Web development tools and to begin the process of platform
API definition. It would be a mistake to commit to too many APIs in our
first release. We need to get more feedback from consumers. We know of
several major development efforts that will be picking up WTP 1.0. This
should generate a lot of useful feedback and enable us to commit to more
APIs for WTP 1.1. 

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 06:16 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	<wtp-dev-bounces@xxxxxxxxxxx>
Subject	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
-----Original Message-----
From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]On
Behalf Of Arthur Ryman
Sent: Wednesday, May 18, 2005 2:24 PM
To: General discussion of project-wide or architectural issues.
Cc: General discussion of project-wide or architectural issues.; wtp-dev-bounces@xxxxxxxxxxx
Subject: RE: [wtp-dev] PMC decision on project and server API enhancements


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
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev