Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350639 - simplify maintaining compatibility with older Eclipse platform releases
Summary: simplify maintaining compatibility with older Eclipse platform releases
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: 3.7   Edit
Assignee: Steffen Pingel CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on: 350385 360301
Blocks:
  Show dependency tree
 
Reported: 2011-06-28 18:16 EDT by Steffen Pingel CLA
Modified: 2012-02-16 16:38 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steffen Pingel CLA 2011-06-28 18:16:26 EDT 
The policy described under http://wiki.eclipse.org/Mylyn/Integrator_Reference#Deciding_on_a_version states that the most recent two platform releases are supported but we have seen continued interest from integrators for supporting older Eclipse platform releases. The current policy helps to control testing overhead and enables consumption of recent platform API enhancements and we should continue to follow it. Still, where feasible we should encapsulated platform difference, e.g. through utility methods, to help integrators reduce maintenance burden.
Comment 1 Steffen Pingel CLA 2012-02-16 16:38:28 EST 
Provisional packages have been promoted to API and the feature structure of Mylyn Commons has been improved. This ensures that extensions can now fully rely on API and should not require access to internal or provisional packages any longer. 

The next Mylyn 3.8 release will be part of the Eclipse Juno LTS release and will be the reference for long term binary backwards compatibility with the Mylyn 3.x stream.