I vote for leaving PTP 3.0 end of September so we don't procrastinate any more,
assuming there are no other reasons to delay.
We could always have a point release (e.g. 3.0.1) to update PTP plugins with support for product changes, assuming there are no API changes in PTP
(which don't sound probable).
I have some other deadlines in October and I'd rather get the PTP release done first.
But, I can be outvoted. :-)
...Beth
Beth Tibbitts (859) 243-4981 (TL 545-4981)
Eclipse Parallel Tools Platform http://eclipse.org/ptp
Mailing Address: IBM Corp., Coldstream Research Campus, 745 West New Circle Road, Lexington, KY 40511
<graycol.gif>Dave Wootton---07/31/2009 06:55:23 AM---Hi
| <ecblank.gif> To | <ecblank.gif> ptp-dev@xxxxxxxxxxx | <ecblank.gif> cc | <ecblank.gif> | <ecblank.gif> Subject | <ecblank.gif> [ptp-dev] PTP 3.0 release date change | <ecblank.gif> | <ecblank.gif> | |
Hi
I'm looking at schedules for some IBM product software which some PTP work
I'm doing is dependent upon. The schedules for PTP 3.0 and this software
line up better if the PTP 3.0 release is delayed until the end of October.
Is it acceptable to everyone here if we delay PTP 3.0 until the end of
October?
Dave
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________