Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] non-API breaking change required for 6.0 branch to fix a bug

It's something that's always been in our policy. After the last maintenance release a branch remains open and anyone can ask for an official build. We need to deal with realities of vendors still supporting old streams and still wanting to benefit from fixes from the community.

On Thu, Apr 8, 2010 at 10:49 AM, John Cortell <rat042@xxxxxxxxxxxxx> wrote:
What's the point of putting a fix into the 5.x branch? Even the 6.x one...are we ever going to release another 6.0.x build? I guess I'm questioning whether we should have changes in the code that are not published in any milestone of official release.


At 09:45 AM 4/8/2010, Alena Laskavaia wrote:
Customer wants up to fix a bug about multiple breakpoints support
in exiting product which is based on CDT 6.0 (and 5.0). To fix this I
have to add a setter method
into MIBreakpoint class to set a line number (which is non breaking API change).
Any objections if I do it on branches (well on trunk too)? I should
not cause any breakage for anybody because the
only danger is if somebody would extend the class and add a method
with the same name, but people cannot do because field is package
private so they cannot create a setter for it anyway.
cdt-dev mailing list

cdt-dev mailing list

Back to the top