Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
AW: [wtp-dev] PMC decision on project and server API enhancements

Ted,

 

The requirements group has drafted a document to describe the 1.1 release – we will discuss that document in next weeks pmc call and make the full document public afterwards.

 

The current planning is to base WTP 1.1 on Eclipse 3.1 (likely on a bugfix release) and enable the majority of the provisional api to become platform quality api. We believe it would be most valuable to ship the version 1.1 towards the end of this year. If we need Eclipse 3.2 functionality for achieving the desired level of flexibility for our project structure then we probably have to stay with provisional api for the 1.1 release in this area.

 

Jochen

 

-----Urspr√ľngliche Nachricht-----
Von: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] Im Auftrag von Ted Bashor
Gesendet: Mittwoch, 18. Mai 2005 22:35
An: General discussion of project-wide or architectural issues.
Betreff: 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.


Back to the top