[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] remote API change
|
Well, in theory, the policy is that you can¹t make API changes in the dot
releases, only in the June releases. That¹s so the community doesn¹t get
surprised when they upgrade to Neon.1 and things start failing badly.
I¹ve been playing with CDT¹s new build system APIs and I¹ve managed to do
it without changing API, just adding to it. Java 8¹s default methods on
interfaces are a saviour. Would it be possible to make these changes
without removing API?
I have some things for an o.e.remote minor release in serial and the
console but have managed to work around them for Neon.1. Given this is RC2
week, I thought it would be too late to schedule a release for it, and
it¹s big enough to be considered a feature change. My recommendation is to
wait for Neon.1. It¹s only three months away. But do what you need to do.
Doug.
On 2016-08-30, 9:53 PM, "ptp-dev-bounces@xxxxxxxxxxx on behalf of Greg
Watson" <ptp-dev-bounces@xxxxxxxxxxx on behalf of g.watson@xxxxxxxxxxxx>
wrote:
>Doug,
>
>I¹ve made some API changes to remote.core and remote.ui that it would be
>nice to have in Neon.1. It¹s a major change, so the version should really
>be changed to 3.0.0. Do you think this needs a release review for the
>whole of PTP? What do think is the best way to go?
>
>Thanks,
>Greg
>_______________________________________________
>ptp-dev mailing list
>ptp-dev@xxxxxxxxxxx
>To change your delivery options, retrieve your password, or unsubscribe
>from this list, visit
>https://dev.eclipse.org/mailman/listinfo/ptp-dev
