Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[mylyn-reviews-dev] Breaking API in 2.0.1

Hi all,

Please note that if you're currently consuming (or contemplating consuming) the generic Remote API in Mylyn 2.0, we'll have breaking changes in 2.0.1 [1] [2]. This is an exception from EDP, but it's in the service of quality. While it's technically possible to avoid breaking API, but it would create extra work and risk that we really would like to avoid. This does mean of course that consumers of Kepler will have to rely on an upcoming SR release to preserve API compatibility.

My guess is that we don't *have* any external consumers of this part of the API at this point, at least ones that have shipped, but if I'm wrong about that, please send a msg to list asap and we'll figure out a way to support your needs. 

cheers,

Miles

[1] 413480: [regression] Fix notification mechanism https://bugs.eclipse.org/bugs/show_bug.cgi?id=413480
[2] https://git.eclipse.org/r/#/c/15004/

Miles T. Parker | Tasktop Labs | Tasktop Technologies  
email: miles.parker@xxxxxxxxxxx 
web: http://tasktop.com  | blog: http://milesparker.blogspot.com  

Committer: Eclipse Mylyn Reviews, R4E, Virgo
Lead: Eclipse Mylyn MFT, AMP 

Are you passionate about innovation and excellence and interested in joining our team? Tasktop, voted one of the Best Companies to Work for in British Columbia, is hiring!



Back to the top