Jump to: navigation, search

Difference between revisions of "Development Resources/Project Plan/XML"

Line 59: Line 59:
  
 
Note that if your HTML blocks contain non-XML-parseable HTML, you'll want to enclose them in a CDATA section, e.g.,
 
Note that if your HTML blocks contain non-XML-parseable HTML, you'll want to enclose them in a CDATA section, e.g.,
   <introduction><![[CDATA[ ... ]]></introduction>
+
   <introduction><![CDATA[ ... ]]></introduction>
  
 
Obviously, the milestone, theme and appendix elements can be repeated as many times as necessary.   
 
Obviously, the milestone, theme and appendix elements can be repeated as many times as necessary.   
Line 65: Line 65:
 
== XML Schema ==
 
== XML Schema ==
  
The XML Schema for the above spec is still in flux. See {{bug|215301}} for the latest.
+
The XML Schema for the above spec is still in flux. See {{bug|243303}} for the latest.
  
* [https://bugs.eclipse.org/bugs/attachment.cgi?id=95055&action=edit projectplan.xsd], 2008-04-07
+
* [https://bugs.eclipse.org/bugs/attachment.cgi?id=109320 projectplan.xsd], 2008-08-06
  
 
==Bugs as Plan Items==
 
==Bugs as Plan Items==
Line 75: Line 75:
  
 
==Specifying the Plan==
 
==Specifying the Plan==
The project plan xml file is placed in the project's website CVS. The project meta-data item "projectplanurl" is then defined to point to that xml file.  Use the [http://portal.eclipse.org/ portal] to modify the [http://www.eclipse.org/projects/dev_process/project-status-infrastructure.php project meta-data].
+
The project plan xml file is placed in the project's website CVS. The project meta-data item "projectplanurl" is then defined to point to that xml file.  Use the [http://portal.eclipse.org/ portal] to modify the [http://www.eclipse.org/projects/dev_process/project-status-infrastructure.php project meta-data].
 +
 
 +
Note that in addition for specifying your "current plan" in the Portal, {{bug|238434}} is open requesting an ability to render arbitrary XML project plans as HTML.
  
 
== Examples ==
 
== Examples ==

Revision as of 10:37, 6 August 2008

As per a resolution from the Board that led to bug 215301, all projects are required to provide their current project plan in the following XML format.

XML Template

<?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">
   <release projectid="technology.dash" version="1.0"/>
   <introduction>
     ...html...
   </introduction>
   <release_deliverables>
     ...html...
    </release_deliverables>
   <release_milestones>
      <preamble>...html...</preamble>
      <milestone date="7/1/2008" milestone="M1">...optional html...</milestone>
      <milestone date="8/1/2008" milestone="M2">...optional html...</milestone>
      <milestone date="9/1/2008" milestone="RC1">...optional html...</milestone>
      <milestone date="6/28/2009" milestone="1.0"/>
      <postamble>...html...</postamble>
   </release_milestones>
   <target_environments>
     ...html...
     <internationalization>
       ...html...
     </internationalization>
   </target_environments>
   <compatibility_with_previous_releases>
     ...html...
   </compatibility_with_previous_releases>
   <themes_and_priorities>
     <preamble>
       ...html...
     </preamble>
     <theme name="Appealing to the Broader Community">
        <description>...(optional) html...</description>
        <committed bugzilla="...(recommended) bugzilla search url...">
           ...(optional alternate) html...</committed>
        <proposed bugzilla="...(recommended) bugzilla search url...">
           ...(optional alternate) html...</proposed>
        <deferred bugzilla="...(recommended) bugzilla search url...">
           ...(optional alternate) html...</deferred>
     </theme>
     <theme name="Design for Extensibility">
        <description>...(optional) html...</description>
        <committed bugzilla="...(recommended) bugzilla search url...">
           ...(optional alternate) html...</committed>
        <proposed bugzilla="...(recommended) bugzilla search url...">
           ...(optional alternate) html...</proposed>
        <deferred bugzilla="...(recommended) bugzilla search url...">
           ...(optional alternate) html...</deferred>
     </theme>
   </themes_and_priorities>
   <appendix name="Project Refactoring">
     ...html...
   </appendix>	
 </plan>

Note that if your HTML blocks contain non-XML-parseable HTML, you'll want to enclose them in a CDATA section, e.g.,

 <introduction><![CDATA[ ... ]]></introduction>

Obviously, the milestone, theme and appendix elements can be repeated as many times as necessary.

XML Schema

The XML Schema for the above spec is still in flux. See bug 243303 for the latest.

Bugs as Plan Items

The goal of the bugzilla queries is to support the use of bugzilla items for planning. The project team should assign target milestones to each bug, including both defects and enhancements. Additionally, the team should assign keywords (or keywords-in-titles) to each bug entry in order to classify them into themes. The bugzilla queries would then be, e.g., "all 2.6M1, 2.6M2, 2.6M3, ..., 2.6 bugs with keyword 'designforextensibility'", etc.

If a project chooses not to use bugzilla item for planning (contrary to collective wisdom of the senior Eclipse project leads), the project plan format allows arbitrary html text paragraph(s) instead.

Specifying the Plan

The project plan xml file is placed in the project's website CVS. The project meta-data item "projectplanurl" is then defined to point to that xml file. Use the portal to modify the project meta-data.

Note that in addition for specifying your "current plan" in the Portal, bug 238434 is open requesting an ability to render arbitrary XML project plans as HTML.

Examples

  • Dash Sample