plans/ecf.plan.3.10.xml - gerrit/www.eclipse.org/ecf - Git at Google

 <?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.10" />
 	<introduction>
 		<html:div>
 			<html:p>
 			    ECF released version 3.9.0 as part of the <html:a href="https://wiki.eclipse.org/Luna">Luna Simultaneous Release</html:a>, and in August 2014
 			    ECF <html:a href="http://www.eclipse.org/ecf/downloads.php">released version 3.9.1</html:a>.
 			    The plan below describes the intended work for ECF 3.10, which will occur on or before the <html:a href="https://wiki.eclipse.org/Mars">Mars Simultaneous Release</html:a> scheduled
 			    for June 2015.
 			</html:p>
 		</html:div>
 	</introduction>
 	<release_deliverables>
 		<html:div>
 			<html:p>
 				The major ECF 3.10 release deliverables are as follows:
 			</html:p>
 		</html:div>
 	</release_deliverables>
 	<release_milestones>
 		<preamble>
 			<html:div>
 			The ECF 3.10 milestones will generally occur approximately 1 week prior to the Mars Simultaneous Release Milestone Schedule.
 			</html:div>
 		</preamble>
 		<milestone date="1/30/2015" milestone="M5">
 			<html:div>ECF 3.10.0 M5</html:div>
 		</milestone>
 		<milestone date="3/13/2015" milestone="M6">
 			<html:div>ECF 3.10.0 M6</html:div>
 		</milestone>
 		<milestone date="4/25/2014" milestone="M7">
 			<html:div>ECF 3.10.0 M7</html:div>
 		</milestone>
 		<milestone date="5/15/2014" milestone="RC1">
 			<html:div>ECF 3.10.0 RC1</html:div>
 		</milestone>
 		<milestone date="5/22/2014" milestone="RC2">
 			<html:div>ECF 3.10.0 RC2</html:div>
 		</milestone>
 		<milestone date="5/29/2014" milestone="RC3">
 			<html:div>ECF 3.10.0 RC3</html:div>
 		</milestone>
 		<milestone date="6/5/2014" milestone="RC4">
 			<html:div>ECF 3.10.0 RC4</html:div>
 		</milestone>
 		<postamble>
 			<html:div></html:div>
 		</postamble>
 	</release_milestones>
 	<target_environments>
 		<html:div>
 			ECF's target environments are:
 			<html:ul>
 				<html:li>Eclipse Tools and Eclipse-based tooling/products</html:li>
 				<html:li>Eclipse-based Applications</html:li>
 				<html:li>Eclipse RCP-based Applications</html:li>
 				<html:li>Equinox servers</html:li>
 				<html:li>Karaf-based servers</html:li>
 			</html:ul>
 		</html:div>
 		<internationalization>
 			<html:div>ECF doesn't perform internationalization directly, although
 				we develop our plugins following
 				common rules about string externalization to make the automation possible
 			</html:div>
 		</internationalization>
 	</target_environments>
 	<compatibility_with_previous_releases>
 		<html:div>
 			<html:p>
 				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
 				<html:pre>x-internal:=true</html:pre>
 				in their Export-Package declaration. As an example,
 				with the following declaration in the org.eclipse.ecf MANIFEST.MF
 			</html:p>
 			<html:pre>Export-Package: org.eclipse.ecf.core,
 				org.eclipse.ecf.internal.core;x-internal:=true
        </html:pre>
 			<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
 				constraints.</html:p>
 		</html:div>
 	</compatibility_with_previous_releases>
 	<themes_and_priorities>
 		<preamble>
 			<html:div></html:div>
 		</preamble>
 		<theme name="Tooling for ECF Remote Services">
 			<description>
 				<html:p>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:
 				</html:p>
 				<html:p>
 					<html:ul>
 					  <html:li>Evaluate and Import the GSoC 2014 work into an official plugin. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454062">(enhancement)</html:a></html:li>
 					  <html:li>Remote services information. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454609">(tracking)</html:a></html:li>
 						<html:ul>
     		              <html:li>Provide a dedicated ECF remote services view. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454610">(enhancement)</html:a></html:li>
         		          <html:li>Show available data from the remote service. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454612">(enhancement)</html:a></html:li>
             		      <html:li>Hook remote service discovery into UI notification. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454615">(enhancement)</html:a></html:li>
                 		  <html:li>Provide statistics on remote service registrations. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454616">(enhancement)</html:a></html:li>
          	      	 	  <html:li>Extend PDE Registry views to provide RS info. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454618">(enhancement)</html:a></html:li>
 						</html:ul>
 					</html:ul>
 				</html:p>
 			</description>
 		</theme>
 		<theme name="Maintenance">
 			<description>
 			https://bugs.eclipse.org/bugs/show_bug.cgi?id=455300
 				<html:p>
 				Update existing providers to more recent upstream versions (jmdns, zookeeper, apache httpclient, others).
 					<html:ul>
 					  <html:li><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=378350">zookeeper</html:a></html:li>
 					  <html:li><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=326228">jmdns</html:a></html:li>
 					</html:ul>
     			</html:p>
     			<html:p>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.
     				<html:ul>
 					  <html:li><html:a href="http://eclip.se/3k">ECF 3.10.0 Releng Bugs</html:a></html:li>
     	              <html:li><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=396457">Move build to Tycho-based build</html:a></html:li>
     	              <html:li><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454632">Update releng to use Java 8.</html:a></html:li>
     	              <html:li><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=429939">Better support automated creation of Karaf distribution meta-data.</html:a></html:li>
    	                  <html:li><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=456052">Use java6 pack200 and avoid problems with embedded jars</html:a></html:li>
      	            </html:ul>
     			</html:p>
 				<html:p>
 				ECF UI maintenance <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454620">(tracking)</html:a>
    					<html:ul>
     	              <html:li>Overhaul of the current communications perspective</html:li>
         	          <html:li>Rename of perspective, provide logo</html:li>
             	      <html:li>Gear perspectives towards remote services</html:li>
 					</html:ul>
     			</html:p>
 			</description>
 		</theme>
 		<theme name="New ECF Providers">
 			<description>
 				<html:p>Add the following new ECF providers
 				<html:ul>
 				<html:li>Websockets provider (remote services distribution). <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=426186">(enhancement)</html:a></html:li>
 				<html:li>Etcd-based provider (discovery).  <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=440824">(enhancement)</html:a></html:li>
 				<html:li>Example custom HTTP+REST/JSON|xml providers (TBD)</html:li>
 				</html:ul>
 			    </html:p>
 			</description>
 		</theme>
 	</themes_and_priorities>
 </plan>
	<?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.10" />
	<introduction>
	<html:div>
	<html:p>
	ECF released version 3.9.0 as part of the <html:a href="https://wiki.eclipse.org/Luna">Luna Simultaneous Release</html:a>, and in August 2014
	ECF <html:a href="http://www.eclipse.org/ecf/downloads.php">released version 3.9.1</html:a>.
	The plan below describes the intended work for ECF 3.10, which will occur on or before the <html:a href="https://wiki.eclipse.org/Mars">Mars Simultaneous Release</html:a> scheduled
	for June 2015.
	</html:p>
	</html:div>
	</introduction>
	<release_deliverables>
	<html:div>
	<html:p>
	The major ECF 3.10 release deliverables are as follows:
	</html:p>
	</html:div>
	</release_deliverables>
	<release_milestones>
	<preamble>
	<html:div>
	The ECF 3.10 milestones will generally occur approximately 1 week prior to the Mars Simultaneous Release Milestone Schedule.
	</html:div>
	</preamble>
	<milestone date="1/30/2015" milestone="M5">
	<html:div>ECF 3.10.0 M5</html:div>
	</milestone>
	<milestone date="3/13/2015" milestone="M6">
	<html:div>ECF 3.10.0 M6</html:div>
	</milestone>
	<milestone date="4/25/2014" milestone="M7">
	<html:div>ECF 3.10.0 M7</html:div>
	</milestone>
	<milestone date="5/15/2014" milestone="RC1">
	<html:div>ECF 3.10.0 RC1</html:div>
	</milestone>
	<milestone date="5/22/2014" milestone="RC2">
	<html:div>ECF 3.10.0 RC2</html:div>
	</milestone>
	<milestone date="5/29/2014" milestone="RC3">
	<html:div>ECF 3.10.0 RC3</html:div>
	</milestone>
	<milestone date="6/5/2014" milestone="RC4">
	<html:div>ECF 3.10.0 RC4</html:div>
	</milestone>
	<postamble>
	<html:div></html:div>
	</postamble>
	</release_milestones>
	<target_environments>
	<html:div>
	ECF's target environments are:
	<html:ul>
	<html:li>Eclipse Tools and Eclipse-based tooling/products</html:li>
	<html:li>Eclipse-based Applications</html:li>
	<html:li>Eclipse RCP-based Applications</html:li>
	<html:li>Equinox servers</html:li>
	<html:li>Karaf-based servers</html:li>
	</html:ul>
	</html:div>
	<internationalization>
	<html:div>ECF doesn't perform internationalization directly, although
	we develop our plugins following
	common rules about string externalization to make the automation possible
	</html:div>
	</internationalization>
	</target_environments>
	<compatibility_with_previous_releases>
	<html:div>
	<html:p>
	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
	<html:pre>x-internal:=true</html:pre>
	in their Export-Package declaration. As an example,
	with the following declaration in the org.eclipse.ecf MANIFEST.MF
	</html:p>
	<html:pre>Export-Package: org.eclipse.ecf.core,
	org.eclipse.ecf.internal.core;x-internal:=true
	</html:pre>
	<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
	constraints.</html:p>
	</html:div>
	</compatibility_with_previous_releases>
	<themes_and_priorities>
	<preamble>
	<html:div></html:div>
	</preamble>
	<theme name="Tooling for ECF Remote Services">
	<description>
	<html:p>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:
	</html:p>
	<html:p>
	<html:ul>
	<html:li>Evaluate and Import the GSoC 2014 work into an official plugin. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454062">(enhancement)</html:a></html:li>
	<html:li>Remote services information. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454609">(tracking)</html:a></html:li>
	<html:ul>
	<html:li>Provide a dedicated ECF remote services view. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454610">(enhancement)</html:a></html:li>
	<html:li>Show available data from the remote service. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454612">(enhancement)</html:a></html:li>
	<html:li>Hook remote service discovery into UI notification. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454615">(enhancement)</html:a></html:li>
	<html:li>Provide statistics on remote service registrations. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454616">(enhancement)</html:a></html:li>
	<html:li>Extend PDE Registry views to provide RS info. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454618">(enhancement)</html:a></html:li>
	</html:ul>
	</html:ul>
	</html:p>
	</description>
	</theme>
	<theme name="Maintenance">
	<description>
	https://bugs.eclipse.org/bugs/show_bug.cgi?id=455300
	<html:p>
	Update existing providers to more recent upstream versions (jmdns, zookeeper, apache httpclient, others).
	<html:ul>
	<html:li><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=378350">zookeeper</html:a></html:li>
	<html:li><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=326228">jmdns</html:a></html:li>
	</html:ul>
	</html:p>
	<html:p>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.
	<html:ul>
	<html:li><html:a href="http://eclip.se/3k">ECF 3.10.0 Releng Bugs</html:a></html:li>
	<html:li><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=396457">Move build to Tycho-based build</html:a></html:li>
	<html:li><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454632">Update releng to use Java 8.</html:a></html:li>
	<html:li><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=429939">Better support automated creation of Karaf distribution meta-data.</html:a></html:li>
	<html:li><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=456052">Use java6 pack200 and avoid problems with embedded jars</html:a></html:li>
	</html:ul>
	</html:p>
	<html:p>
	ECF UI maintenance <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=454620">(tracking)</html:a>
	<html:ul>
	<html:li>Overhaul of the current communications perspective</html:li>
	<html:li>Rename of perspective, provide logo</html:li>
	<html:li>Gear perspectives towards remote services</html:li>
	</html:ul>
	</html:p>
	</description>
	</theme>
	<theme name="New ECF Providers">
	<description>
	<html:p>Add the following new ECF providers
	<html:ul>
	<html:li>Websockets provider (remote services distribution). <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=426186">(enhancement)</html:a></html:li>
	<html:li>Etcd-based provider (discovery). <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=440824">(enhancement)</html:a></html:li>
	<html:li>Example custom HTTP+REST/JSON\|xml providers (TBD)</html:li>
	</html:ul>
	</html:p>
	</description>
	</theme>
	</themes_and_priorities>
	</plan>