Location: /localsite//ecf/plans/ecf.plan.3.7.xml
Meta-data Tag: projectplanurl

	<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
<plan plan-format="1.0" xmlns="http://www.eclipse.org/project/plan"
	xmlns:html="http://www.w3.org/1999/xhtml" name="Eclipse Communication Framework">
	<release projectid="rt.ecf" version="3.7" />
				Previously, ECF has had three major releases:
				ECF 1.0.0 as part of <html:a href="http://wiki.eclipse.org/index.php/Europa_Simultaneous_Release">Europa Simultaneous Release</html:a>, 
				ECF 2.0.0 as part of <html:a href="http://wiki.eclipse.org/Ganymede_Simultaneous_Release">Ganymede Simultaneous Release</html:a>, 
				ECF 3.0.0 as part of <html:a href="http://wiki.eclipse.org/Galileo_Simultaneous_Release">Galileo Simultaneous Release</html:a>, 
				and ECF 3.6.1 as part of <html:a href="http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan</html:a>. 
				This plan describes the work for ECF 3.7.0, which will occur in October 8, 2013.
				The major ECF 3.7 release deliverables are as follows:
					<html:li>Enable easier creation and use of Equinox+ECF remote services-based Server
						Runtimes by introducing support for use of HttpService/Servlets for OSGi Remote Service provider implementation</html:li>
					<html:li>Fully implement OSGi 5 Remote Services (RS) and Remote Service Admin (RSA) standard (chapters 13 and 122 in OSGi enterprise specification)</html:li>
					<html:li>Improve DNSSD discovery provider</html:li>
					<html:li>Improve and Extend the ECF Example Applications, with
						special emphasis on OSGi remote services and remote service admin examples

			No milestones.
		<milestone date="10/8/2013" milestone="3.7.0">
			<html:div>ECf 3.7.0 release</html:div>
			ECF's target environments are:
				<html:li>Eclipse-based Applications</html:li>
				<html:li>Eclipse RCP</html:li>
				<html:li>Other Equinox-Based Runtimes (e.g. Equinox servers)</html:li>
			<html:div>ECF doesn't perform internationalization directly, although
				we develop our plugins following
				common rules about string externalization to make the automation possible
				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
				in their Export-Package declaration. As an example,
				with the following declaration in the org.eclipse.ecf MANIFEST.MF
			<html:pre>Export-Package: org.eclipse.ecf.core,
			<html:p>The org.eclipse.ecf.core package is API, and the
				org.eclipse.ecf.internal.core package is not</html:p>
			<html:p>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
		<theme name="OSGI Remote Services and RSA Standards">
				<html:p>Implement OSGi R5 version of Remote Services Admin specification (impl of OSGI
					Remote Services Admin spec). 
		<theme name="ECF Providers">
				<html:p>Add support for Servlet/HttpService-based remote service providers