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.
ECF released version 3.9.0 as part of the Luna Simultaneous Release, and in August 2014 ECF released version 3.9.1. The plan below describes the intended work for ECF 3.10, which will occur on or before the Mars Simultaneous Release scheduled for June 2015.
The major ECF 3.10 release deliverables are as follows:
ECF 3.10.0 M5
ECF 3.10.0 M6
ECF 3.10.0 M7
ECF 3.10.0 RC1
ECF 3.10.0 RC2
ECF 3.10.0 RC3
ECF 3.10.0 RC4
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.
Consumers of ECF Remote Services can/could benefit from the creation of Eclipse-based tooling for declaring, implementing, testing, debugging, deploying, monitoring, and managing Remote Services. A major theme for ECF will be creation of tooling to ease the burden on the consumer of ECF's Remote Services implementation. Tooling:
Update existing providers to more recent upstream versions (jmdns, zookeeper, apache httpclient, others).
ECF Releng , Build and Distributions. Ongoing maintenance with respect to release engineering. Move build to Tycho-based build. Update releng to use Java 8. Better support automated creation of Karaf distribution meta-data. Routinely build maven repo.
ECF UI maintenance (tracking)
Add the following new ECF providers
Back to the top