[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-dev] CDT 7.0 for Helios
|
Freescale also takes, develops against, and deploys the stack in its
entirety. Thus, API breakage is not a big concern for us...as long as
they're not behavioral breaks, as those go undetected at build time and
ultimately are discovered through a runtime bug (not good).
John
At 02:18 PM 11/4/2009, Doug Schaefer wrote:
Thanks, Ken, you don't have to
wait for me :).
A lot of the reason behind sticking with 6.1 was to show that we are
managing our APIs carefully and not changing them. We've been bad at that
in the past and sooner or later we need to change that. And adopting the
API tooling as we did last release to monitor this was a great first
step.
But we've heard from a number of committers now that we're still not
done. While we are managing APIs better, we still have technical issues
with the APIs themselves and we need to resolve that.
So I'm open to making this CDT 7.0. At the least, we should upversion the
plug-ins that need to API changes to 7.0. And I'd prefer that the CDT
"marketing" number always equal the highest version of our
plug-ins.
But, we do need to hear from the ISV community on how this impacts them.
Do any vendors want to use plug-ins built against CDT 6.0 and have them
to work against the Helios release. At Wind River, we've never done that,
we always take a whole new stack from Eclipse.
Doug.
On Wed, Nov 4, 2009 at 3:05 PM,
<ken.ryall@xxxxxxxxx>
wrote:
- Doug may have been planning to start talking about this but it was on
my mind this morning so I wanted to follow up on the list with something
we discussed on the CDT call yesterday: making the next release of CDT
for Helios (due next summer) version 7.0 instead of version 6.1.
- This means that there would be some API breakage in a few focused
areas but that we would take care to document the changes so people
integrating with CDT would know what to expect. Although it is impossible
to know if anyone if using a given API, it is likely that the APIs we
discussed arent currently used or are in very limited use. Of course the
6.0.x stream would be unaffected.
- It would be good to hear from people who integrate with CDT to find
out which APIs are in common use so we can limit the impact of any
proposed changes.
- Thanks - Ken
- _______________________________________________
- cdt-dev mailing list
- cdt-dev@xxxxxxxxxxx
-
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev