Saying Eclipse 3.2 is available is a bit misleading. Eclipse M2 milestone of 3.2 is what is available.
It seems like it is very early to force teams to have to worry about split streams and about WTP 1.5 deliverables when we really have just started on WTP 1.0. There is a ton of code churn going in because of the removal of multiple modules per project and the project facets, as well as the removal of the .deployables. These items need the utmost attention to ensure the overall quality is moving forward. Would you take a development resource off of the WTP 1.0 stream so that they could make a fix for an early adopter of WTP 1.5? The 1.0 release of WTP is on Eclipse 3.1.1. That is what we should be trying to deliver. The only reason we should start a new stream early is if Eclipse has finished a feature request of ours for 3.2 and so that we could get an early start on the game for WTP 1.5. I don't think that is the case just yet. So, to summarize, my concerns would be with delivering a solid, high quality WTP 1.0 on the Eclipse 3.1.1 release before having to worry about appeasing any early adopters of Eclipse 3.2.
Thanks,
John Lanuti
Software Engineer, IBM Rational
[EMAIL PROTECTED]
t/l 441-7861
"I know this lady way down in my country.
She is so pretty that my eyes throw disguises at me.
Now we will sit and we'll wonder about our future,
But now I'm thinking that today sounds fine to me." - Of A Revolution
| Jeffrey Liu <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 10/05/2005 05:12 PM
|
|
In Thursday's WTP status telecon, I would like to discuss the possibility of opening up a WTP 1.5 code stream. Now that Eclipse 3.2 is available, vendors will start building products on top of Eclipse 3.2. For those vendors who also use WTP, they'll need a WTP build that works on top Eclipse 3.2. However, such WTP build does not exist. We are still building on top of Eclipse 3.1.1 and we have yet to test WTP on top of Eclipse 3.2. To encourage the adoption of WTP and to allow these vendors to make progress, I would like to propose we open up a WTP 1.5 code stream and start building WTP on top of Eclipse 3.2.
Initially, we can keep the 1.0 code stream and the 1.5 code stream common as much as possible by only fixing Eclipse 3.2 API changes. That way, the effort to maintain dual code streams can be kept to a minimal. Your suggestions/comments/concerns are welcome.
Thanks,
Jeffrey Liu_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
