Project_Plan.xml

<?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="Marketplace Client (MPC)">
  <release projectid="technology.packaging.mpc" version="1.1"/>
  <introduction>
    <html:div>Marketplace Client provides a rich client for installing solutions listed on Eclipse Marketplace.  MPC provides a workflow for finding and installing solutions, layering on top of the Eclipse P2 and providing a streamlined and simplified workflow that does not require users to enter and manage update sites.   </html:div>
  </introduction>
  <release_deliverables>
    <html:div>Release 1.1 will will update the functionality of the existing MPC to improve the usability and make it easier for more people to use MPC.</html:div>
  </release_deliverables>
  <release_milestones>
    <preamble>
      <html:div></html:div>
    </preamble>
    <milestone date="3/18/2011" milestone="M6"><html:div>Feature completion, will be available as part of Indigo M6</html:div></milestone>
    <milestone date="5/6/2011" milestone="M7"><html:div>Response to community feedback</html:div></milestone>
    <milestone date="5/20/2011" milestone="RC1"><html:div>Updates to documentation</html:div></milestone>
    <milestone date="5/27/2011" milestone="RC2"><html:div>Release Candidate</html:div></milestone>
    <milestone date="6/3/2011" milestone="RC3"><html:div>Release Candidate</html:div></milestone>
    <milestone date="6/10/2011" milestone="RC4"><html:div>Release Candidate</html:div></milestone>
    <milestone date="6/22/2011" milestone="Final"><html:div>First Release (1.1)</html:div></milestone>
	<postamble>
		<html:div xmlns="http://www.w3.org/1999/xhtml">
			<p><a name="ramp-down"><b>Ramp Down</b></a></p>
			<p>After RC1 is released, builds will be produced weekly until the final 1.1 release. In the RC
			phase only bugs marked P1 or higher or severity major or higher will be fixed. APIs will not
			change except to address critical fixes requiring approval of at least two committers.</p>
		</html:div> 
	</postamble>
  </release_milestones>
  <target_environments>
    <html:div>The plan is to support the operating systems supported by the EPP packages.</html:div>
    <internationalization>
      <html:div>The content from Marketplace is English.  No plans for internationalization in this release.</html:div>
    </internationalization>
  </target_environments>
  <compatibility_with_previous_releases>
    <html:div>Release 1.1 will be compatible with Eclipse 3.6, Eclipse 3.7 and Eclipse 4.0.</html:div>
  </compatibility_with_previous_releases>
  <themes_and_priorities>
    <preamble>
      <html:div>This release of MPC is focused on making it easier for more people to use Marketplace Client.</html:div>
    </preamble>
    <theme name="Get More People to Use MPC">
      <description><html:div>The current version of MPC requires the user to know that the Marketplace Client is accessible from the Eclipse Help menu.   We want to implement features that 
      make MPC accessible from other sources. Specific items:
      <html:ol><html:li>End user should be able to drag and drop a URL to a running Eclipse installation to start an MPC install for a particular product.  <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=336156">[336156]</html:a><html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=336154">[336154]</html:a></html:li>
      <html:li>End user should be able to share via e-mail or twitter an Eclipse MPC solution.<html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=336160">[336160]</html:a></html:li>   
      </html:ol></html:div></description>
    </theme>
    <theme name="Usability">
      <description><html:div>Make it easier for users to discover relevant solutions within MPC. Specific items:
      <html:ol><html:li>MPC should show tags that have been specified for a product listing.<html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=336149">[336149]</html:a></html:li>
      <html:li>Different third party catalogs should be listed as icons at the bottom of the wizard and switching should be done via selecting the icon.<html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=336157">[336157]</html:a></html:li>     
 	  <html:li>Third party catalogs should be allowed to provide more branding, so the end user can see when they are in a different catalog. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=336159">[336159]</html:a></html:li>
      </html:ol></html:div></description>
    </theme>
   <theme name="Eclipse 4">
      <description><html:div>MPC will be tested and supported on Eclipse 4.1 release.
      </html:div></description>
    </theme>        
    <theme name="Other">
      <description><html:div>
      Specific items:
      <html:ol><html:li>Third party catalogs should be discovered from the Eclipse Marketplace server.  <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=328605">[328605]</html:a></html:li>
      <html:li>MPC should be able to use alternative p2 repositories to resolve dependencies. <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=332073">[332973]</html:a></html:li>
      <html:li>Splitting code and configuration of the MPC  <html:a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=313581">[313581]</html:a></html:li>
      
      </html:ol></html:div></description>
    </theme>    
  </themes_and_priorities>
  <!--
  <appendix name="Project Refactoring">
  </appendix>	
  -->
</plan>