Friends of Eclipse,
Eclipse is an open source community that benefits millions of developers around the world each and every day! During the month of September, we are asking you to give back to our wonderful open source community. All donations will be used to improve Eclipse technology. Your contribution counts!
We thank you for this gesture, and for giving back to our community.
Previously, ECF has had three major releases: ECF 1.0.0 as part of Europa Simultaneous Release, ECF 2.0.0 as part of Ganymede Simultaneous Release, ECF 3.0.0 as part of Galileo Simultaneous Release, and ECF 3.3.0 as part of Helios Simultaneous Release. This plan describes the work for ECF 3.6, which will occur in June, 2011 as part of the Indigo Simultaneous Release.
The major ECF 3.6 release deliverables are as follows:
ECF 3.6 API Freeze
ECF 3.6 Feature Freeze
Indigo GA/ECF 3.6
ECF has a policy of maintaining API backward compatibility with minor and service releases. API is considered all exported packages (i.e. packages that do not have
x-internal:=truein their Export-Package declaration. As an example, with the following declaration in the org.eclipse.ecf MANIFEST.MF
Export-Package: org.eclipse.ecf.core, org.eclipse.ecf.internal.core;x-internal:=true
The org.eclipse.ecf.core package is API, and the org.eclipse.ecf.internal.core package is not
Only with major releases (e.g. 2.0.0, 3.0.0) are incompatible API changes to be introduced (e.g. refactorings, renames), and even then only after discussion among multiple committers. For the parts of ECF used by the Platform (e.g. the core and file transfer bundles), NO incompatible API changes will be introduced, even for major releases, in order to maintain the platform backward compatibility constraints.
Implement Remote Services Admin specification (impl of OSGI Remote Services Admin spec).
Add XML-RPC-based provider
Extend DNSSD provider
Add SIP provider
Back to the top