Jump to: navigation, search

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

m (add reference to bug 248672 re: galileo%2B / galileo+ not being properly encoded)
(Embedded Queries)
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
In the [[Modeling Project]], we're all about Agile development, so the intent is to make the overhead as lightweight as possible. Consistency while supporting variety.
 
In the [[Modeling Project]], we're all about Agile development, so the intent is to make the overhead as lightweight as possible. Consistency while supporting variety.
 +
 +
== Galileo Flag ==
  
 
Here's how to identify bugs in your [[Development_Resources/Project_Plan|plan.xml]] using the [http://bugs.eclipse.org/247191 galileo] flag:
 
Here's how to identify bugs in your [[Development_Resources/Project_Plan|plan.xml]] using the [http://bugs.eclipse.org/247191 galileo] flag:
Line 7: Line 9:
 
* Deferred Items: mark with <b style="color:red">galileo-</b>
 
* Deferred Items: mark with <b style="color:red">galileo-</b>
  
 +
== Planned vs. Unplanned ==
  
Next, to group your plan items by theme, it's suggested that you use the Status Whiteboard. To do so, query for one or more bugs, click the <b>Change Several Bugs at Once</b> link, select the bugs you want to change, and set a Status Whiteboard value for those bugs:
+
To differentiate things planned up front vs. great ideas added along the way, it's suggested you use the <b style="color:blue">plan</b> keyword.
 +
 
 +
== Group By Theme ==
 +
 
 +
To group your plan items by theme, it's suggested that you use the Status Whiteboard. To do so, query for two or more bugs, then scroll to the bottom of the list.
  
 
{| border="1" align="center"
 
{| border="1" align="center"
 
|-
 
|-
 
| valign="top"|
 
| valign="top"|
[[Image:Eclipse-bugzilla-status-whiteboard.png|border]]
+
[[Image:Change-several-bugs-at-once.png]]
 
|}
 
|}
  
Finally, you need to embed queries in your plan.xml. [http://dev.eclipse.org/viewcvs/index.cgi/www/modeling/emf/emf/project-info/plan.xml?root=Eclipse_Website&content-type=text%2Fplain&view=co Here's an example].
+
Click the <b>Change Several Bugs at Once</b> link, select the bugs you want to change, and set a Status Whiteboard value for those bugs:
 +
 
 +
{| border="1" align="center"
 +
|-
 +
| valign="top"|
 +
[[Image:Eclipse-bugzilla-status-whiteboard.png]]
 +
|}
 +
 
 +
== Embedded Queries ==
 +
 
 +
Finally, you need to embed queries in your plan.xml. [http://dev.eclipse.org/viewcvs/index.cgi/www/modeling/emf/emf/project-info/plan.xml?root=Eclipse_Website&revision=1.12&content-type=text%2Fplain Here's an example].
 +
 
 +
== Testing your plan.xml ==
 +
 
 +
* You can commit your changes into CVS, wait 30-60 seconds, and refresh your your plan doc's URL, eg., [http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/emf/cdo/project-info/plan.xml&component=CDO modeling.emf.cdo plan.xml].
 +
 
 +
* Or, you can [http://intellectualcramps.blogspot.com/2008/09/generating-eclipse-project-plan.html use the XSL Tools project] to render a plan locally before you commit it.
 +
 
 +
== Gotchas ==
  
If your query works in a browser but returns nothing when viewed through the project plan renderer, it maybe be because the renderer is stripping parts of your query. See {{bug|248672}}, or this [http://dev.eclipse.org/viewcvs/index.cgi/www/modeling/emf/emf/project-info/plan.xml?root=Eclipse_Website&r1=1.11&r2=1.12 this workaround].
+
If your query works in a browser but returns nothing when viewed through the project plan renderer, it maybe be because the renderer is stripping parts of your query. See {{bug|248672}} or [http://dev.eclipse.org/viewcvs/index.cgi/www/modeling/emf/emf/project-info/plan.xml?root=Eclipse_Website&r1=1.11&r2=1.12 this workaround].
  
 
[[Category:Modeling]] [[Category:Releng]]
 
[[Category:Modeling]] [[Category:Releng]]

Latest revision as of 01:26, 23 November 2008

In the Modeling Project, we're all about Agile development, so the intent is to make the overhead as lightweight as possible. Consistency while supporting variety.

Galileo Flag

Here's how to identify bugs in your plan.xml using the galileo flag:

  • Committed Items: mark with galileo+, and assign to a reusable milestone, eg. "M1", "M2", ... "M7" or "RC"
  • Proposed Items: mark with galileo+, and assign to either the "---" target milestone, or the actual release version, eg., for EMF, 2.5; for OCL, 1.3.
  • Deferred Items: mark with galileo-

Planned vs. Unplanned

To differentiate things planned up front vs. great ideas added along the way, it's suggested you use the plan keyword.

Group By Theme

To group your plan items by theme, it's suggested that you use the Status Whiteboard. To do so, query for two or more bugs, then scroll to the bottom of the list.

Change-several-bugs-at-once.png

Click the Change Several Bugs at Once link, select the bugs you want to change, and set a Status Whiteboard value for those bugs:

Eclipse-bugzilla-status-whiteboard.png

Embedded Queries

Finally, you need to embed queries in your plan.xml. Here's an example.

Testing your plan.xml

  • You can commit your changes into CVS, wait 30-60 seconds, and refresh your your plan doc's URL, eg., modeling.emf.cdo plan.xml.

Gotchas

If your query works in a browser but returns nothing when viewed through the project plan renderer, it maybe be because the renderer is stripping parts of your query. See bug 248672 or this workaround.