[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] Next PTP release - 2.2 vs. 3.0?
|
Thanks, Greg - this clears the murk considerably!
Jay
----- Original Message -----
From: "Greg Watson" <g.watson@xxxxxxxxxxxx>
To: "Parallel Tools Platform general developers" <ptp-dev@xxxxxxxxxxx>
Sent: Tuesday, May 05, 2009 8:25 AM
Subject: Re: [ptp-dev] Next PTP release - 2.2 vs. 3.0?
Beth & Jay,
Eclipse defines when version numbers change:
- The major segment number must be increased when a plug-in makes
breaking changes to its API.
- The minor segment number must be incremented when a plug-in changes
in an "externally visible" way.
- The service segment number must be incremented whenever there have
been changes to a plug-in between releases that are not visible in its
API.
The 2.1 release didn't involve any breaking API changes, whereas the
next release will. I think this requires us to use 3.0.
Regards,
Greg
On May 1, 2009, at 12:00 PM, Jay Alameda wrote:
Beth,
I'd like to try to understand the rationale a little bit better - it
appears that ptp2.1 was the inconsistent one, assuming that we bump
PTP major version everytime we bump CDT. Do we have any concise
notion of what it took to increment major versions before (not to
mention the changes going into the 2.2 or 3.0 release from 2.1?). I
think I'm looking for something that we could state in a few
sentences, rather than lists of changes which can be hard to
comprehend as to the magnitude of changes...
For instance, changing the relationship of RDT and CDT so that we
have smoother operation of remote operations would be huge -- and
one possible argument for a major version change ("remote is the
default").
Just wondering - quite often, I have found version changes to be
quite mysterious indeed....
Jay
----- Original Message -----
From: Beth Tibbitts
To: Parallel Tools Platform general developers
Sent: Thursday, April 30, 2009 1:49 PM
Subject: [ptp-dev] Next PTP release - 2.2 vs. 3.0?
We've gone back and forth regarding what to call the next release:
2.2 or 3.0 (so far we have called it 2.2 in the wiki, for lack of
decisiveness :) )
I propose we pin this down, and call it 3.0, for the following
reasons:
1. It will require an upgrade to the Eclipse release (3.5/Galileo)
as well as the CDT release (6.0 - which goes up a whole point from
5.x)
2. Changing the major release number when the underlying Eclipse/CDT
changes would make it easier to distinguish which releases go with
which
3. maturity and usability of RDT for remote usage will strengthen
4. More resource managers coming as well
For some history
PTP 1.0 - Eclipse 3.1, CDT 3.0
PTP 1.1 - Eclipse 3.2 (Callisto), CDT 3.1
PTP 2.0 - Eclipse 3.3 (Europa), CDT 4.0
PTP 2.1 - Eclipse 3.4 (Ganymede), CDT 5.0
proposed:
PTP 3.0 - Eclipse 3.5 (Galileo), CDT 6.0
So actually, this fits the pattern of bumping the major release
number every two Eclipse releases :-)
For timeframe, so far in monthly PTP meetings we've estimated this
for the August/September timeframe.
Comments?
...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
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
