This commit was manufactured by cvs2svn to create branch 'Phx1-0'.
diff --git a/build/install.html b/build/install.html
index 1eee97f..0aa6ea7 100644
--- a/build/install.html
+++ b/build/install.html
@@ -28,7 +28,7 @@
 download page</a>.
 Otherwise, follow along below for detailed steps for installing BIRT.
 <p>
-The instructions here are for the Release 1.0.1 (and later) builds. Please use 1.0.1 or later 
+The instructions here are for the Release 2.0 (and later) builds. Please use 2.0 or later 
 instead of the earlier milestone or stable builds.
 <h1>Java</h1>
 <p>
@@ -42,27 +42,51 @@
 <li>Eclipse 3.0.1, and 3.0.2.
 <li>GEF 3.0.1.
 <li>EMF 2.0.3.
-<li>GEF JRE 1.4.
+<li>JRE 1.4.2.
 </ul>
 And
 <ul>
 <li>Eclipse 3.1.
 <li>GEF 3.1.
 <li>EMF 2.1.
-<li>GEF JRE 1.4/JRE 1.5.
+<li>JRE 1.4.2/JRE 1.5.
 </ul>
 
 
-<p class="caution"><span class="caution-head">Note:</span> Additionally, If you are installing the 2.0 Milestone 1 release you will need
-the following downloads</p>
 
+
+<p class="caution"><span class="caution-head">Note:</span> Additionally, If you are installing the 2.0 you will need
+the following downloads</p>
 <ul>
-<li><a href="http://www.w3.org/2002/06/sacjava-1.3.zip">SAC 1.3</a>.
-<li><a href="http://www.w3.org/2002/06/flutejava-1.3.zip">Flute 1.2</a>.
+<li><a href="http://www.lowagie.com/iText/download.html">iText 1.3</a>.
 </ul>
 <p>
-The SAC APIs are discussed at <a href="http://www.w3.org/Style/CSS/SAC/">Cascading Style Sheets SAC: The Simple API for CSS</a><br> 
-The sac.jar and flute.jar files need to be copied to the plugins\org.eclipse.birt.report.model_x.x.x\lib directory.
+The iText APIs are discussed at <a href="http://www.lowagie.com/iText/">iText Homepage</a><br> 
+The itext-1.3.jar file needs to be copied to the plugins/org.eclipse.birt.report.engine.emitter.pdf_version/lib directory.
+</p>
+<p>
+Also download Apache Axis 1.2.1. from <a href=http://www.apache.org/dyn/closer.cgi/ws/axis/1_2_1>Apache</a>
+and extract only the six jars listed below into the plugins/org.eclipse.birt.report.viewer_version/birt/WEB-INF/lib directory.
+<ul>
+<li>axis.jar 
+<li>axis-ant.jar 
+<li>commons-discovery-0.2.jar 
+<li>jaxrpc.jar 
+<li>saaj.jar 
+<li>wsdl4j-1.5.1.jar 
+</ul>
+</p>
+<p>
+Lastly download prototype.js v1.4.0 from <a href=http://dev.conio.net/repos/prototype/dist/>dev.conio.net</a>. Copy it into the plugins/org.eclipse.birt.report.viewer_version/birt/ajax/lib directory.
+</p>
+
+<p class="caution"><span class="caution-head">Birt Runtime Note: </span>If you are installing the BIRT Runtime,
+The above files will need to be copied to the birt-runtime-2_0_0\Web Viewer Example directory structure.
+<br>Copy itext-1.3.jar to /Web Viewer Example/plugins/org.eclipse.birt.report.engine.pdf/lib.
+<br>Copy prototype.js to /Web Viewer Example/ajax/lib.
+<br>Copy Axis jars to the /Web Viewer Example/WEB-INF/lib
+<br>
+If you are using the birt.war, you will need to extract it and add the above files.
 </p>
 <br>
 
diff --git a/db/main.html b/db/main.html
index 4feb3f7..4909313 100644
--- a/db/main.html
+++ b/db/main.html
@@ -48,7 +48,6 @@
 <ul>
   <li>Apache Derby database, which is included in the BIRT download </li>
   <li><a href="#MySQL">Scripts to load a MySQL database</a></li>
-  <li><a href="#MS-access">Microsoft Access Database</a></li>
 </ul>
 
 <h2><a name="MySQL">MySQL Version</a></h2>
diff --git a/deploy/birtengine.zip b/deploy/birtengine.zip
index 9f3c165..efcb678 100644
--- a/deploy/birtengine.zip
+++ b/deploy/birtengine.zip
Binary files differ
diff --git a/deploy/engine.html b/deploy/engine.html
index e4a589d..108fb15 100644
--- a/deploy/engine.html
+++ b/deploy/engine.html
@@ -123,6 +123,11 @@
 the engine located in the full BIRT install: 
 /eclipse/plugins/org.eclipse.birt.report.viewer_1.0.1/birt.</p>
 
+<p class="caution"><span class="caution-head">Release 2.0 M3  Note:</span> Please use the
+birt-runtime download when setting the engine home.  The engine home should be set to
+installedlocation/birt-runtime-x_y_z/Report Engine
+</p>
+
 <h2>Emitter Configuration</h2>
 
 <p>An &quot;emitter&quot; is the component of the report engine that produces output. BIRT provides two emitters: HTML and PDF. You'll want to configure the HTML 
diff --git a/deploy/viewer-deploy.html b/deploy/viewer-deploy.html
index bf63ced..ac3db6d 100644
--- a/deploy/viewer-deploy.html
+++ b/deploy/viewer-deploy.html
@@ -33,6 +33,7 @@
   <li>Look under the  birt-runtime-&lt;version#&gt; directory and locate the &quot;Web Viewer Example&quot; directory.</li>
   <li>Copy the Web Viewer Example directory to the webapps directory of your 
 Tomcat installation. For ease of reference,  rename the directory to &quot;birt-viewer&quot;.</li>
+  <li>Copy additional files to the directory structure as described in the BIRT Runtime <a href=http://www.eclipse.org/birt/index.php?page=build/install.html>Note</a> 
   <li>Stop, then restart Tomcat.</li>
   <li>Display the Tomcat manager application to check that the 
 viewer is deployed: <a href="http://localhost:8080/manager/html">
@@ -46,10 +47,11 @@
 need to use a context entry within the server.xml file to indicate the 
 deployment location. See Tomcat documentation for details. </p>
 
+<br>
 <h1>Install your JDBC Drivers</h1>
 
 <p>Add the jar files for your JDBC drivers  to the Viewer. They  go in the following directory:</p>
-<p> birt-viewer/WEB-INF/plugins/org.eclipse.birt.report.data.oda.jdbc/drivers</p>
+<p> birt-viewer/plugins/org.eclipse.birt.report.data.oda.jdbc/drivers</p>
 <p>(Note: you must install the drivers both into 
   the Eclipse-based design environment and the deployed viewer environment; these 
 two environments do not share files.)</p>
@@ -58,7 +60,7 @@
 <p>We'll test the viewer further using one of the example reports created for the &quot;Classic Models&quot; database. Note that Classic Models database is included in the birt runtime distribution so no further set-up is required. Follow these steps: 
 <ul>
   <li>Click on the following link to download the example report design, 
-  <a href="../examples/SalesInvoice.rptdesign" target="_blank">SalesInvoice.rptdesign</a> into another browser window. Use the &quot;Save as...&quot; command from the file menu to save the report into the birt-viewer/report directory.</li>
+  <a href="../examples/solution/SalesInvoice.rptdesign" target="_blank">SalesInvoice.rptdesign</a> into another browser window. Use the &quot;Save as...&quot; command from the file menu to save the report into the birt-viewer/report directory.</li>
   <li>If you've installed everything in its default location, then click on the 
   following link. If you've changed anything, then copy the following URL into 
   your browser and make the needed changes.<pre class="code-block"><a href="http://localhost:8080/birt-viewer/frameset?__report=report%5CSalesInvoice.rptdesign" target="_blank">http://localhost:8080/birt-viewer/frameset?__report=report%5CSalesInvoice.rptdesign</a>
diff --git a/deploy/viewer-use.html b/deploy/viewer-use.html
index 941424d..21d017e 100644
--- a/deploy/viewer-use.html
+++ b/deploy/viewer-use.html
@@ -166,6 +166,12 @@
 
 <h2>List of Options </h2>
 
+<p class="caution">
+<span class="caution-head">Release 2.0 Note</span>: 
+The __frame, __toolbar, and __navigation options are obsolete and will only work with
+the 1.0.1 release. 
+</p>
+
 <p>The available viewer options include:</p>
 
 <table class="simple-table">
diff --git a/images/errordata.jpg b/images/errordata.jpg
deleted file mode 100644
index f705071..0000000
--- a/images/errordata.jpg
+++ /dev/null
Binary files differ
diff --git a/images/rcp.jpg b/images/rcp.jpg
deleted file mode 100644
index 8501b2e..0000000
--- a/images/rcp.jpg
+++ /dev/null
Binary files differ
diff --git a/main.html b/main.html
index 949b019..4a3cfc2 100644
--- a/main.html
+++ b/main.html
@@ -80,6 +80,22 @@
 <h1>What's New</h1>
 
 <dl class="date-list">
+<dt>January 22</dt>
+<dd><a href="http://download.eclipse.org/birt/downloads">BIRT 2.0</a>
+is now available for download.  Read about the feature set at <a href="project/notable2.0.html">Notable Features - BIRT 2.0</a> </dd>
+
+
+<dt>January 16</dt>
+<dd><a href="http://www.eclipse.org/birt/index.php?page=project/pmc.html">The BIRT PMC</a> is pleased to announce 
+that Mike Fox, from IBM / Rational, has joined the Committee.</dd>
+
+<dt>January 4</dt>
+<dd><a href="http://download.eclipse.org/birt/downloads">BIRT 2.0 Release Candidate</a>
+is available for download.</dd>
+
+<dt>December 7</dt>
+<dd><a href="http://download.eclipse.org/birt/downloads">BIRT 2.0 Milestone 3</a>
+can now be downloaded.  Read about the feature set at <a href="project/notable2.0M3.html">Notable Features - BIRT 2.0 M3</a> </dd>
 
 
 <dt>November 3</dt>
@@ -113,15 +129,6 @@
 <a href="presos/Eclipse BIRT Project Mastering BIRT.pdf">Mastering BIRT</a> - Exploring BIRT Extensions <br>  
 <a href="presos/Eclipse BIRT Plugin Map.pdf">BIRT Plugin Map</a> - BIRT Projects and Extension Points<br>  
 </dd>
-
-<dt>August 17</dt>
-<dd><a href="notable.html">Notable Features - BIRT 1.0.1</a>  Take a look at some of 
-the features that are supplied with BIRT 1.0.1
-</dd>
-
-<dt>August 5</dt>
-<dd><a href="http://download.eclipse.org/birt/downloads">BIRT 1.0.1</a>
-is available for download.  An example of deploying BIRT using the Eclipse Rich Client Platform (RCP) is also available.</dd>
   
 </dl>
 <b><a href="whatsnew.html">More of What's New...</a></b>
diff --git a/project-page-paragraph.html b/project-page-paragraph.html
new file mode 100644
index 0000000..fe9c6c8
--- /dev/null
+++ b/project-page-paragraph.html
@@ -0,0 +1,11 @@
+<p><b><a href="/birt/">Business Intelligence and Reporting Tools</a></b> <br/>
+<p>The BIRT project provides a business intelligence and reporting framework that
+ integrates easily with existing infrastructure and applications.  
+ The project provides extensible tools and APIs for building and deploying reports 
+ to environments ranging from Java/J2EE to PHP -- both web and desktop, 
+ including Eclipse-based applications. BIRT is based on open source standards, 
+ and allows designers to provide functionality for data mining and analysis, 
+ drill through and SVG rendered interactive graphs.  
+ The BIRT platform is extensible, facilitating the input of new data sources, 
+ export of custom formats and support of custom report components. 
+</p>
diff --git a/project/PlanAndDeliverables.html b/project/PlanAndDeliverables.html
index 020fc49..cb56a02 100644
--- a/project/PlanAndDeliverables.html
+++ b/project/PlanAndDeliverables.html
@@ -22,7 +22,7 @@
 <h1>Project Plan</h1>
 
 <dl class="arrow-list">
-<dt><a href="project_plan_R2_0_0_Draft.html">2.0 Project Plan</a></dt>
+<dt><a href="project_plan_R2_0_0.html">2.0 Project Plan</a></dt>
 <dd>The plans for the 2.0 release.</dd>
 
 <dt><a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS">BIRT Project Specifications</a></dt>
@@ -38,8 +38,8 @@
 <dt>Friday, September 16, 2005</dt><dd> BIRT 2.0 M1</dd>
 <dt>Monday, October 24, 2005</dt><dd> BIRT 2.0 M2 </dd>
 <dt>Monday, November 21, 2005</dt><dd> BIRT 2.0 M3</dd> 
-<dt>Monday, December 5, 2005</dt><dd> BIRT 2.0 Release Candidate</dd> 
-<dt>Friday, December 30, 2005</dt><dd> BIRT 2.0 Final</dd> 
+<dt>Monday, December 30, 2005</dt><dd> BIRT 2.0 Release Candidate</dd> 
+<dt>Friday, January 20, 2006</dt><dd> BIRT 2.0 Final</dd> 
 </dl>
 
 <h1>Milestone Planning</h1>
@@ -49,8 +49,8 @@
 
 <dt>BIRT 2.0 M1 </dt><dd> <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+M1&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=enhancement&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Features</a> List, <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+M1&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Bug</a> Fixes</dd>
 <dt>BIRT 2.0 M2 </dt><dd> <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+M2&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=enhancement&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Features</a> List, <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+M2&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Bug</a> Fixes  <a href="notable2.0M2.html"> Notable Features - BIRT 2.0 M2</a></dd>
-<dt>BIRT 2.0 M3 </dt><dd><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+M3&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=enhancement&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Features</a> List, <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+M3&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Bug</a> Fixes</dd>
-<dt>BIRT 2.0 FINAL </dt><dd> <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+Final&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=enhancement&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Features</a> List, <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+Final&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Bug</a> Fixes</dd>
+<dt>BIRT 2.0 M3 </dt><dd><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+M3&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=enhancement&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Features</a> List, <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+M3&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Bug</a> Fixes <a href="notable2.0M3.html"> Notable Features - BIRT 2.0 M3</a></dd>
+<dt>BIRT 2.0 FINAL </dt><dd> <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+Final&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=enhancement&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Features</a> List, <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+Final&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Bug</a> Fixes <a href="notable2.0.html"> Notable Features - BIRT 2.0</a></dd>
 
 <br>
 <dt>BIRT 2.0 </dt><dd> <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+Final&target_milestone=2.0.0+M1&target_milestone=2.0.0+M2&target_milestone=2.0.0+M3&target_milestone=2.0.0+M4&target_milestone=2.0.0+M5&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=enhancement&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">All Feautres</a> Scheduled, <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+Final&target_milestone=2.0.0+M1&target_milestone=2.0.0+M2&target_milestone=2.0.0+M3&target_milestone=2.0.0+M4&target_milestone=2.0.0+M5&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">All Bug</a> Fixes Scheduled</dd>
diff --git a/project/images/Datasource1.jpg b/project/images/Datasource1.jpg
new file mode 100644
index 0000000..a6de843
--- /dev/null
+++ b/project/images/Datasource1.jpg
Binary files differ
diff --git a/project/images/PropertyBinding.jpg b/project/images/PropertyBinding.jpg
new file mode 100644
index 0000000..1a55523
--- /dev/null
+++ b/project/images/PropertyBinding.jpg
Binary files differ
diff --git a/project/images/ScriptEditor.jpg b/project/images/ScriptEditor.jpg
new file mode 100644
index 0000000..0614cc3
--- /dev/null
+++ b/project/images/ScriptEditor.jpg
Binary files differ
diff --git a/project/images/TemplateItem.jpg b/project/images/TemplateItem.jpg
new file mode 100644
index 0000000..11f27ed
--- /dev/null
+++ b/project/images/TemplateItem.jpg
Binary files differ
diff --git a/project/images/TemplateItemDetail.jpg b/project/images/TemplateItemDetail.jpg
new file mode 100644
index 0000000..05f7d82
--- /dev/null
+++ b/project/images/TemplateItemDetail.jpg
Binary files differ
diff --git a/project/images/TemplatePublish.jpg b/project/images/TemplatePublish.jpg
new file mode 100644
index 0000000..fd6dfff
--- /dev/null
+++ b/project/images/TemplatePublish.jpg
Binary files differ
diff --git a/project/images/TemplateUsage.jpg b/project/images/TemplateUsage.jpg
new file mode 100644
index 0000000..2978032
--- /dev/null
+++ b/project/images/TemplateUsage.jpg
Binary files differ
diff --git a/project/images/aggr1a.jpg b/project/images/aggr1a.jpg
new file mode 100644
index 0000000..edc3a11
--- /dev/null
+++ b/project/images/aggr1a.jpg
Binary files differ
diff --git a/project/images/aggr2a.jpg b/project/images/aggr2a.jpg
new file mode 100644
index 0000000..830a385
--- /dev/null
+++ b/project/images/aggr2a.jpg
Binary files differ
diff --git a/project/images/chart1a.jpg b/project/images/chart1a.jpg
new file mode 100644
index 0000000..bd6d1fc
--- /dev/null
+++ b/project/images/chart1a.jpg
Binary files differ
diff --git a/project/images/chart2a.jpg b/project/images/chart2a.jpg
new file mode 100644
index 0000000..b8adc17
--- /dev/null
+++ b/project/images/chart2a.jpg
Binary files differ
diff --git a/project/images/chart3a.jpg b/project/images/chart3a.jpg
new file mode 100644
index 0000000..a6d473a
--- /dev/null
+++ b/project/images/chart3a.jpg
Binary files differ
diff --git a/project/images/export1.jpg b/project/images/export1.jpg
new file mode 100644
index 0000000..d35fcba
--- /dev/null
+++ b/project/images/export1.jpg
Binary files differ
diff --git a/project/images/export3a.png b/project/images/export3a.png
new file mode 100644
index 0000000..1134f58
--- /dev/null
+++ b/project/images/export3a.png
Binary files differ
diff --git a/project/images/interactcol.jpg b/project/images/interactcol.jpg
new file mode 100644
index 0000000..0e03f26
--- /dev/null
+++ b/project/images/interactcol.jpg
Binary files differ
diff --git a/project/images/javaevent1.jpg b/project/images/javaevent1.jpg
new file mode 100644
index 0000000..c5b1fbd
--- /dev/null
+++ b/project/images/javaevent1.jpg
Binary files differ
diff --git a/project/images/javaevent2.jpg b/project/images/javaevent2.jpg
new file mode 100644
index 0000000..636e2a0
--- /dev/null
+++ b/project/images/javaevent2.jpg
Binary files differ
diff --git a/project/images/javaevent3.jpg b/project/images/javaevent3.jpg
new file mode 100644
index 0000000..ec4b5d6
--- /dev/null
+++ b/project/images/javaevent3.jpg
Binary files differ
diff --git a/project/images/lib3a.jpg b/project/images/lib3a.jpg
new file mode 100644
index 0000000..fd766c7
--- /dev/null
+++ b/project/images/lib3a.jpg
Binary files differ
diff --git a/project/images/lib5a.jpg b/project/images/lib5a.jpg
new file mode 100644
index 0000000..c5f34b5
--- /dev/null
+++ b/project/images/lib5a.jpg
Binary files differ
diff --git a/project/images/templ2a.jpg b/project/images/templ2a.jpg
new file mode 100644
index 0000000..633db0e
--- /dev/null
+++ b/project/images/templ2a.jpg
Binary files differ
diff --git a/project/images/templ4a.jpg b/project/images/templ4a.jpg
new file mode 100644
index 0000000..adcd454
--- /dev/null
+++ b/project/images/templ4a.jpg
Binary files differ
diff --git a/project/images/templ5a.jpg b/project/images/templ5a.jpg
new file mode 100644
index 0000000..ade6caa
--- /dev/null
+++ b/project/images/templ5a.jpg
Binary files differ
diff --git a/project/images/templsnippet.jpg b/project/images/templsnippet.jpg
new file mode 100644
index 0000000..e60d7a9
--- /dev/null
+++ b/project/images/templsnippet.jpg
Binary files differ
diff --git a/project/images/toc.jpg b/project/images/toc.jpg
new file mode 100644
index 0000000..ede1ca1
--- /dev/null
+++ b/project/images/toc.jpg
Binary files differ
diff --git a/project/images/url2a.jpg b/project/images/url2a.jpg
new file mode 100644
index 0000000..64106c6
--- /dev/null
+++ b/project/images/url2a.jpg
Binary files differ
diff --git a/project/images/url3a.jpg b/project/images/url3a.jpg
new file mode 100644
index 0000000..b220c40
--- /dev/null
+++ b/project/images/url3a.jpg
Binary files differ
diff --git a/project/images/xml2.jpg b/project/images/xml2.jpg
new file mode 100644
index 0000000..ce2d38e
--- /dev/null
+++ b/project/images/xml2.jpg
Binary files differ
diff --git a/project/images/xml3.jpg b/project/images/xml3.jpg
new file mode 100644
index 0000000..827f5ec
--- /dev/null
+++ b/project/images/xml3.jpg
Binary files differ
diff --git a/project/new.gif b/project/new.gif
new file mode 100644
index 0000000..3ef5f5e
--- /dev/null
+++ b/project/new.gif
Binary files differ
diff --git a/project/notable2.0.html b/project/notable2.0.html
new file mode 100644
index 0000000..4b53a9f
--- /dev/null
+++ b/project/notable2.0.html
@@ -0,0 +1,165 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 transitional//EN">
+<html>
+
+<head>
+<title>New and Notable Features within BIRT 2.0</title>
+<link rel="stylesheet" href="../style/compose.css" type="text/css"/>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+
+<body>
+
+<p class="head">BIRT Project</p>
+<p class="subhead">New and Notable BIRT 2.0</p>
+
+<h1>General</h1>
+<p>The BIRT Team is pleased announce the release of BIRT 2.0.</p>
+<p>BIRT now supports HTML pagination, CSV output, and a Table Of Contents with the supplied BIRT Viewer.  In addition, features such as Libraries, Templates, Multi-Pass aggregates, flexible Charting Wizard and XML as a data source all contribute to making BIRT 2.0 a powerful platform for your reporting needs.</p>
+<p>This release represents the culmination of a community-driven development cycle that has facilitated the development of quite a list of features and functions.  Some of these features are highlighted below, but the complete list for 2.0 is available
+<a href=http://www.eclipse.org/birt/index.php?page=project/project_plan_R2_0_0.html>here</a></p>
+<p>The BIRT Team would like to thank the BIRT community for the valuable feedback and support you have provided.
+</p>
+<h1>New BIRT Viewer</h1>
+<p>Traversing a large HTML report to locate a particular piece of information can be cumbersome.  To allow better navigation of report data, BIRT 2.0 features a new and improved Viewer, based on AJAX technology.  The new Viewer paginates the emitted HTML following report design properties, allowing it to display pages on demand via the page controls in the Viewer navigation bar.</p>
+<p>In addition to pagination, the new Viewer supports Table Of Contents (TOC) functionality which allows someone viewing a report to jump to a particular section.  For example, in the Customer Orders report presented below, the HTML spans seven pages.  The TOC is displayed in a collapsible frame to the left of the report and represents a hierarchy of content for the entire report.  Selecting any entry in the TOC automatically loads the desired page.  TOC entries can be nested, as the Order Number is nested below the Customer Number in the example below.</p>
+<p>The TOC is formatted with the standard BIRT Expression Builder.</p>
+<img src="images/toc.jpg" width="768" height="576"/>
+<p>The Viewer also supports data extraction to CSV format.  This is accomplished by clicking the "Export Data" icon located on the toolbar.</p>
+<img src="images/export1.jpg" width="768" height="576"/>
+<p>A dialog is presented allowing the user to select the columns to export to CSV.</p>
+<img src="images/export3a.png" width="370" height="408"/>
+
+<h1>JavaScript/Java Events And Report Debugging</h1>
+<p>BIRT currently supports event scripting using JavaScript.  Event handlers are coded in the BIRT Script Editor, which now supports syntax color-coding and code completion.  The Editor also offers improved access to report item properties.</p>
+<img src="images/ScriptEditor.jpg" width="768" height="576"/>
+<p>BIRT 2.0 has extended the script model to allow coding of event handlers in Java as well as JavaScript.  This feature gives the Java developer greater flexibility when building complex reports.  An additional benefit of coding in Java is the ability to debug the events using the new BIRT Report Launch Configuration under the Java Development Tools (JDT).</p>
+<p>To create a Java event the developer first builds the event Class in Java.</p>
+<img src="images/javaevent1.jpg" width="768" height="576"/>
+<p>Next the Class is assigned to the Event Handler Property for the given Report Item.  In the case illustrated below, the Java Event Handler Class is assigned to a table row.</p>
+<img src="images/javaevent2.jpg" width="768" height="576"/>
+<p>The Report can now be debugged within the JDT.</p>
+<img src="images/javaevent3.jpg" width="768" height="576"/>
+
+
+<h1>Runtime Data Source Property Binding</h1>
+<p>It is often desirable to use one set of credentials for developing a report and separate set(s) for production usage.  BIRT 2.0 accomplishes this using a Data Source Property Binding Wizard, which allows several properties for the data source to be changed at runtime.  For example, the report below uses the Username and Password parameters that are passed to it to connect to the data source.</p>
+<img src="images/Datasource1.jpg" width="768" height="576"/>
+<p>The values used in the wizard can be more than simple parameters, including complex statements built using the Expression Builder.  For example assume we wish to use a test database while in development and a production database when the report is complete.  This can be accomplished by swapping the JDBC Driver URL at run time as shown below.</p>
+<img src="images/PropertyBinding.jpg" width="768" height="576"/>
+
+
+
+
+
+
+<h1>Chart Builder and SVG Output</h1>
+<p>A new chart builder is available in BIRT 2.0.  This wizard is designed to expedite chart development by separating the process into three easy to use dialogs: Select Chart Type, Select Data, and Format Chart.  SVG rendering of charts has also been added.</p>
+<img src="images/chart1a.jpg" width="768" height="576"/>
+<p><i>Select Chart Type.</i></p>
+<img src="images/chart2a.jpg" width="591" height="573"/>
+<p><i><c>Select Chart Data.</c></i></p>
+<img src="images/chart3a.jpg" width="504" height="497"/>
+<p><i>Format Chart.</i></p><br>
+<p>Additional functionality has been added to the Chart wizard to enhance support for user interactivity.  As shown below, additional events and actions have been added to support such things as scripting and drill-through.</p>
+<img src="images/interactcol.jpg" width="627" height="503"/>
+
+<h1>Templates</h1>
+<p>BIRT now provides report developers the ability to build and publish report templates.  Consistent look and feel can be difficult to achieve and maintain when building report applications. In addition, productivity and adoption by a broader range of report developers can be fostered by providing a pre-built report elements. Templates address these concerns and can range from skeletal outlines with predefined themes to complete reports.</p>
+<p>Building a BIRT report template is very similar to building a standard BIRT report.  One notable difference is that items within the report can be converted to template report items, which allow the template creator to set up indications where template user input is required.</p>
+<img src="images/TemplateItem.jpg" width="768" height="576"/>
+<img src="images/TemplateItemDetail.jpg" width="595" height="210"/>
+<p><i>Enter Prompts for Template Users.</i></p><br>
+<p>A new Template Publishing wizard has also been added.  The location of the template directory is configurable.</p>
+<img src="images/TemplatePublish.jpg" width="768" height="576"/>
+<p><i>Publish Wizard.</i></p><br>
+<p>The Template wizard allows the designer to populate a display name, description and image file.  The template is now available to use.</p>
+<img src="images/TemplateUsage.jpg" width="768" height="576"/>
+<p><i>Using a newly Created Template.</i></p><br>
+
+
+<h1>Libraries</h1>
+<p>BIRT 2.0 introduces the concept of libraries to BIRT.  With this feature, commonly used functions and report items can be encapsulated within a library.  These libraries can then be imported into any number of reports for reuse.  For example, a BIRT developer may wish to build a complex scripted data source and then encapsulate it within a BIRT library, freeing other members of the reporting team from implementing the same code.</p>
+<img src="images/lib3a.jpg" width="768" height="576"/>
+<p><i>Building a library.</i></p><br>
+<p>A new project item type is now available for library creation.  By dragging items from the palette to the Report Items node within the library Outline, the report developer can customize these components for reuse.  Data Sources and Sets, Report Parameters, Report Items, Themes, Master Pages and Images can be added to the library.</p>
+<p>After the library is created, it can be shared with report developers, who can import the library into their own designs.</p>
+<img src="images/lib5a.jpg" width="768" height="576"/>
+<p><i>Using a library.</i></p><br>
+<p>The BIRT team has also added a new view to the BIRT perspective for browsing and importing the available libraries.  Existing libraries within the workspace automatically show up in the Library Explorer. (In this screenshot, the Explorer has been pinned to the left side with the Palette and Data Explorer.)</p>
+<p>Using a library is as easy as importing it and then dragging the desired items to required report location.</p>
+<p>Reports that reference libraries automatically update when executed.  This is very useful in cases where business or technical changes require report rework. For example, imagine that a database schema changes or the company logo is altered.  If these details are encapsulated in libraries, only the library would need to change and all referencing reports would be automatically updated to reflect the changes.</p>
+
+<h1>XML ODA</h1>
+<p>Building on the existing drivers that BIRT already supplies, BIRT 2.0 delivers an XML ODA for retrieving XML data.  The data can be streamed or reside within a file.  This driver uses XPath syntax for XML to relational data mapping.</p>
+<img src="images/xml2.jpg" width="800" height="522"/>
+<p><i>Use XPath expression to map an XML node to a row.</i></p><br>
+<img src="images/xml3.jpg" width="800" height="522"/>
+<p><i>Use XPath syntax to map node and attribute values to columns.</i></p><br>
+
+
+<h1>URL Builder</h1>
+<p>BIRT 2.0 offers a new URL Builder to quickly support summary to detail Drill-through linking as well as standard Bookmark and URL creation.</p>
+<img src="images/url3a.jpg" width="768" height="576"/>
+<p><i>Define the URL.</i></p><br>
+<img src="images/url2a.jpg" width="768" height="576"/>
+<p><i>Drill-through Illustration.</i></p><br>
+
+<h1>Multi-pass Aggregate, Sorting and Filtering</h1>
+<p>Several improvements have been added to support advanced aggregate, filtering and sorting of report data.  For example, computed columns can now use aggregate functions.</p>
+<img src="images/aggr1a.jpg" width="768" height="576"/>
+<p><i>Computed column with aggregation.</i></p><br>
+<p>In addition, the group dialog now supports adding multiple sorting and filtering expressions. </p>
+<img src="images/aggr2a.jpg" width="768" height="576"/>
+<p><i>New Filtering and Sorting tabs.</i></p><br>
+
+
+<h1>Improved Report Performance and PDF Fidelity</h1>
+<p>BIRT 2.0 includes an enhanced data engine with the ability to process large data sets via a combination of memory and disk cache. The BIRT team has done tests that show that the engine can now handle reports of well over a million rows with linear response time and bounded memory usage.  BIRT has also incorporated the iText PDF library to improve PDF generation fidelity.</p>
+
+
+<h1>Dynamic Parameters/Cascading Parameters</h1>
+<p>Most applications, which require reporting, will have a need for culling or filtering the data that is used within the report.  This allows tailoring the report to a specific user without the need to highly customize the report design.  This is often done with report parameters that are used within the report logic and/or the SQL query.  The issue, then, becomes how to present and collect the parameter information from the consumer of the report.  BIRT 2.0 addresses this issue by adding sophisticated dynamic and cascading parameter support.</p>
+<p>With the new Dynamic Parameter feature, the report designer can present the consumer a list of options for a parameter that is interactive and based on live content.</p>
+<img src="images/dynp1b.JPG" width="602" height="576"/>
+<p>In the above example, a Dynamic Parameter is created that presents the report user with a list of Countries to choose from.  This is achieved, by allowing the report designer the ability to create a BIRT data set, which can then be used to dynamically populate a parameter list box.</p>
+<img src="images/dynp2b.JPG" width="603" height="564"/>
+<p>In addition to Dynamic Parameters, it is often desirable to present the user a set of interlinked parameter choices.  For example, a user wishes to run a report that displays all of his/her employees that work in the Pasadena office.  You would not want to display a list of all possible employee cities.  Ideally a Country list would be displayed, and then possibly a State/Province, followed finally by a City list.  BIRT 2.0 accomplishes this by delivering a Cascading Parameter Feature.</p>
+<img src="images/dynp3a.JPG" width="605" height="631"/>
+<p>The Cascaded parameter list provides nested selection. In the above example, the Customer’s Country is selected and this choice restricts the Customer’s City choices.  As with Dynamic Parameters, the choices are based on a BIRT Data Set.</p>
+<img src="images/dynp4a.JPG" width="603" height="609"/>
+
+
+<h1>Expression Builder</h1>
+<p>The Expression Builder has been replaced with an improved GUI, which presents a more streamlined and intuitive interface for building JavaScript expressions. The new Expression builder includes features like line numbers, cut and paste functionality, object browsing and tool tips.</p>
+<img src="images/express1.JPG" width="602" height="545"/>
+
+<h1>Importing of Style Sheets</h1>
+<p>While Style Sheets offer a wide range of formatting and design features, with earlier versions of BIRT, styles had to be defined individually within the report design.  To overcome this limitation, BIRT 2.0 delivers the capability to import Style Sheets into the report design, from an external source.</p>
+<img src="images/importcss.JPG" width="601" height="453"/>
+<p>Using this feature, it is now easier to present a consistent look and feel across multiple report designs without having to create separate style instances for each. In addition, the feature makes it possible to easily coordinate report look and with web site look and feel, which can be particularly important when BIRT reports are included in extranets and web portals.</p>
+
+<h1>Report XML Editor</h1>
+<p>Expanding on the capabilities of the Report Designer, a new XML source editor tab is now available to the report designer.  The Source tab presents the entire report design in color-coded XML format, allowing direct modifications the XML design that are persisted immediately.</p>
+<img src="images/xmleditor.JPG" width="798" height="598"/>
+
+<h1>Passing of External Object to Custom Data Sources</h1>
+<p>Often the BIRT engine is embedded in or is part of an existing J2EE application.  The ODA layer, which is responsible for data access, occasionally needs access to objects in the Context of the encapsulating application.  This might include things like security credentials, connection handles, or parameter objects.  To accommodate this requirement, BIRT 2.0 has added a Context Object within the ODA layer, which can be passed in from the external application.  This object can take many forms and can be used for all of the items mentioned above.</p>
+
+<h1>Stored Procedures</h1>
+<p>BIRT now supports calling stored procedures.  Within the Data Set Editor, the stored procedures are now displayed and can be used to build complex Data Sets.</p>
+<img src="images/StoredProcs.JPG" width="603" height="547"/>
+<p>In the above example, "OrdersByProducts" is being called to return a quantity of products sold, based on Product Name, which is passed as a parameter to the stored procedure. </p>
+
+<h1>CLOB/BLOB  Support</h1>
+<p>The Data Set data types have been expanded to include Character Large Object (CLOB) and Binary Large Object (BLOB) items.  In addition to adding support for these types within the ODA framework, these items can now be bound to certain controls within the designer.  CLOB columns can be bound to Text controls and BLOB columns can be bound to Image controls.</p>
+<img src="images/blobtype.JPG" width="603" height="457"/>
+<p>In the example above, the logo image is stored as a BLOB type.  The Image Builder has been enhanced to allow the BLOB image to be retrieved from the database and inserted into an Image control.</p>
+
+
+
+
+
+
+
+</body>
+</html>
\ No newline at end of file
diff --git a/project/notable2.0M2.html b/project/notable2.0M2.html
index 5106935..a78582d 100644
--- a/project/notable2.0M2.html
+++ b/project/notable2.0M2.html
@@ -14,7 +14,7 @@
 
 <h1>General</h1>
 <p>The BIRT team has been hard at work developing BIRT 2.0, which is slated for release late this year and has reached a major milestone.  Milestone 2 has officially been released to the public.  Below is a description of some of the key features that are now available in the M2 build.  Keep in mind, as with all milestone releases, the product continues to evolve.   
-The complete list of features for the final 2.0 release is available at http://www.eclipse.org/birt/index.php?page=project/project_plan_R2_0_0_Draft.html.
+The complete list of features for the final 2.0 release is available at http://www.eclipse.org/birt/index.php?page=project/project_plan_R2_0_0.html.
 </p>
 
 <h1>Dynamic Parameters/Cascading Parameters</h1>
diff --git a/project/notable2.0M3.html b/project/notable2.0M3.html
new file mode 100644
index 0000000..1b9dced
--- /dev/null
+++ b/project/notable2.0M3.html
@@ -0,0 +1,82 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 transitional//EN">
+<html>
+
+<head>
+<title>New and Notable Features within BIRT 2.0 Milestone 3</title>
+<link rel="stylesheet" href="../style/compose.css" type="text/css"/>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+
+<body>
+
+<p class="head">BIRT Project</p>
+<p class="subhead">New and Notable BIRT 2.0 M3</p>
+
+<h1>General</h1>
+<p>The BIRT team moves closer to the final 2.0 release this week by completing Milestone 3.<br><br>
+This Milestone has quite a list of improvements, some of which—like templates and libraries—can help Java report developers improve their productivity and help foster reuse within (and across) organizations. Others, such as the improvements to BIRT’s charting, both extend the functionality available and improve its usability. <br><br>
+As with all milestone releases, keep in mind that the product will continue to evolve.<br>
+The complete list of features for the final 2.0 release is available <a href=http://www.eclipse.org/birt/index.php?page=project/project_plan_R2_0_0.html>here</a>.
+</p>
+
+<h1>Chart Builder and SVG Output</h1>
+<p>A new chart builder is available in M3.  This wizard is designed to expedite chart development by separating the process into three easy to use dialogs: Select Chart Type, Select Data, and Format Chart.  SVG rendering of charts has also been added.</p>
+<img src="images/chart1a.jpg" width="768" height="576"/>
+<p><i>Select Chart Type.</i></p>
+<img src="images/chart2a.jpg" width="591" height="573"/>
+<p><i><c>Select Chart Data.</c></i></p>
+<img src="images/chart3a.jpg" width="504" height="497"/>
+<p><i>Format Chart.</i></p><br>
+<p>Additional functionality has been added to the Chart wizard to enhance support for user interactivity.  As shown below additional events and actions have been added to support such things as scripting and drill-through.</p>
+<img src="images/interactcol.jpg" width="627" height="503"/>
+<h1>Templates</h1>
+<p>BIRT now provides report developers the ability to build and publish report templates.  Consistent look and feel can be difficult to achieve and maintain when building report applications. In addition, productivity and adoption by a broader range of report developers can be fostered by providing a pre-built report elements. Templates address these concerns and can range from skeletal outlines with predefined themes to complete reports.</p>
+<br>
+<p>Building a BIRT report template is very similar to building a standard BIRT report.  One notable difference is that items within the report can be converted to template report items, which allow the template creator to set up indications where template user input is required.</p>
+<img src="images/templ2a.jpg" width="768" height="576"/>
+<img src="images/templsnippet.jpg" width="590" height="202"/>
+<p><i>Enter Prompts for Template Users.</i></p><br>
+<p>The BIRT team has added a Template Publishing wizard to quickly put the template to use.</p>
+<img src="images/templ4a.jpg" width="768" height="576"/>
+<p><i>Publish Wizard.</i></p><br>
+<p>The Template wizard allows the designer to populate a display name, description and image file.  After publishing, the template is available to use within the new report wizard.</p>
+<img src="images/templ5a.jpg" width="768" height="576"/>
+<p><i>Using a newly Created Template.</i></p><br>
+<h1>Libraries</h1>
+<p>Milestone 3 introduces the concept of libraries to BIRT.  With this feature, commonly used functions and report items can be encapsulated within a library.  These libraries can then be imported into any number of reports for reuse.  For example, a BIRT developer may wish to build a complex scripted data source and then encapsulate it within a BIRT library, freeing other members of the reporting team from implementing the same code.</p>
+<img src="images/lib3a.jpg" width="768" height="576"/>
+<p><i>Building a library.</i></p><br>
+<p>A new project item type is now available for library creation.  By dragging items from the palette to the Report Items node within the library Outline, the report developer can customize these components for reuse.  Data Sources and Sets, Report Parameters, Report Items, Themes, Master Pages and Images can be added to the library.</p>
+<br>
+<p>After the library is created, it can be shared with report developers, who can import the library into their own designs.</p>
+<img src="images/lib5a.jpg" width="768" height="576"/>
+<p><i>Using a library.</i></p><br>
+<p>The BIRT team has also added a new view to the BIRT perspective for browsing and importing the available libraries.  Existing libraries within the workspace automatically show up in the Library Explorer. (In this screenshot, the Explorer has been pinned to the left side with the Palette and Data Explorer.)
+Using a library is as easy as importing it and then dragging the desired items to required report location.
+</p>
+<br>
+<p>Reports that reference libraries automatically update when executed.  This is very useful in cases where business or technical changes require report rework. For example, imagine that a database schema changes or the company logo is altered.  If these details are encapsulated in libraries, only the library would need to change and all referencing reports would be automatically updated to reflect the changes.</p>
+<h1>XML ODA</h1>
+<p>Building on the existing drivers that BIRT supplies, M3 delivers an XML ODA for retrieving XML data.  The data can be streamed or reside within a file.  This driver uses XPath syntax for XML to relational data mapping.</p>
+<img src="images/xml2.jpg" width="800" height="522"/>
+<p><i>Use XPath expression to map an XML node to a row.</i></p><br>
+<img src="images/xml3.jpg" width="800" height="522"/>
+<p><i>Use XPath syntax to map node and attribute values to columns.</i></p><br>
+<h1>URL Builder</h1>
+<p>M3 offers a new URL Builder to quickly support summary to detail Drill-through linking as well as standard Bookmark and URL creation.</p>
+<img src="images/url3a.jpg" width="768" height="576"/>
+<p><i>Define the URL.</i></p><br>
+<img src="images/url2a.jpg" width="768" height="576"/>
+<p><i>Drill-through Illustration.</i></p><br>
+<h1>Multi-pass Aggregate, Sorting and Filtering</h1>
+<p>Several improvements have been added to support advanced aggregate, filtering and sorting of report data.  For example, computed columns can now use aggregate functions.</p>
+<img src="images/aggr1a.jpg" width="768" height="576"/>
+<p><i>Computed column with aggregation.</i></p><br>
+<p>In addition, the group dialog now supports adding multiple sorting and filtering expressions.</p>
+<img src="images/aggr2a.jpg" width="768" height="576"/>
+<p><i>New Filtering and Sorting tabs.</i></p><br>
+<h1>Improved PDF and Report Performance</h1>
+<p>M3 includes an enhanced data engine with the ability to process large data sets via a combination of memory and disk cache. The BIRT team has done tests that show that the engine can now handle reports of well over a million rows with linear response time and bounded memory usage.
+<br>BIRT has also incorporated the iText PDF library to improve PDF generation performance.</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/project/pmc.html b/project/pmc.html
index 39aab4f..6dc3633 100644
--- a/project/pmc.html
+++ b/project/pmc.html
@@ -27,7 +27,20 @@
   applications. Paul is currently responsible for coordinating overall product 
   direction and vision for Actuate. He is also a member of the Eclipse 
   Planning and Requirements Councils.</dd>
-  
+
+<dt><i>Michael Fox, IBM / Rational</i></dt> 
+<dd>Mike has over 20 years experience with software product development
+and software project management. Mike has been responsible for developing 
+reporting solutions for several companies. He is now the Technical Lead and 
+Architect for the reporting components of IBM/Rational's Team Products, and 
+involved with reporting work in other parts of IBM Software Group. 
+</dd>
+
+<dt><i>Scott Rosenbaum, Innovent Solutions</i></dt>
+<dd>Scott has been providing professional services consulting in the business 
+  intelligence space for more than seven years and has been involved in software 
+  development for more than 15.</dd>
+
 <dt><i>Jason Weathersby, Actuate</i></dt>
 <dd>Jason has 15 years experience in the software development and consulting fields,
 with in-depth experience in identifying and addressing customer's 
@@ -36,10 +49,7 @@
 Open Source community. 
 </dd>
 
-<dt><i>Scott Rosenbaum, Innovent Solutions</i></dt>
-<dd>Scott has been providing professional services consulting in the business 
-  intelligence space for more than seven years and has been involved in software 
-  development for more than 15.</dd>
+
 </dl>
 
 <h1>Project Leaders</h1>
diff --git a/project/project_plan_R2_0_0.html b/project/project_plan_R2_0_0.html
new file mode 100644
index 0000000..7184540
--- /dev/null
+++ b/project/project_plan_R2_0_0.html
@@ -0,0 +1,776 @@
+<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
+
+<html>
+<head>
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<meta name="Author" content="Eclipse BIRT Project PMC">
+<title>Eclipse BIRT Project - DRAFT 2.0 Plan</title>
+
+</head>
+
+<body>
+
+<p class="head">BIRT Project  2.0 Plan</p>
+<p class="subhead">Last revised 9 December, 2005 <br>
+<img src="/birt/project/new.gif" alt="New since last update" width="12" height="12"> marks interesting changes since the previous draft of 28 September, 2005</p>
+<h2><a name="Introduction"></a>Introduction</h2><p>
+This document lays out the feature and API set for the next feature release of the Eclipse BIRT project after 1.0.1, designated release 2.0.
+<ul>
+  <li><a href="#Deliverables">Release deliverables</a></li>
+  <li><a href="#Milestones">Release milestones</a></li>
+  <li><a href="#TargetOperatingEnvironments">Target operating
+  environments</a></li>
+  <li><a href="#Compatibility">Compatibility with previous releases</a></li>
+  <li><a href="#Themes">Themes</a></li>
+  <li><a href="#Projects">Projects</a></li>
+  <li><a href="#Defects">Defects</a></li>
+</ul>
+
+<p>
+Plans do not materialize out of nowhere, nor are they entirely static. To ensure 
+the planning process is transparent and open to the entire Eclipse community, plans 
+are posted in an embryonic form and then revised from time to time throughout the 
+release cycle. 
+</p>
+
+<p>
+The first part of the plan deals with the important matters of release deliverables, 
+release milestones, target operating environments, and release-to-release compatibility. 
+These are all things that need to be clear for any release, even if no features were 
+to change.
+</p>
+
+<p>
+The remainder of the plan consists of plan items for the projects under the Eclipse 
+BIRT project. Each plan item covers a feature or API that is to be added, or some aspect 
+that is to be improved. Each plan item has its own entry in the Eclipse bugzilla 
+database, with a title and a concise summary (usually a single paragraph) that explains 
+the work item at a suitably high enough level so that everyone can readily understand 
+what the work item is without having to understand the nitty-gritty detail.
+</p>
+
+<p>
+Please send comments about this draft plan to the <a href="mailto:birt-dev@eclipse.org">BIRT 
+Developer</a> mailing list.
+</p>
+
+<h2><a name="Deliverables"></a>Release deliverables</h2>
+
+<p>The release deliverables are:</p>
+<ul>
+  <li>Source code release for Eclipse BIRT, available as versions tagged &quot;R2.0&quot; in 
+the eclipse.org <a href="http://dev.eclipse.org/viewcvs">CVS repository</a>.</li>
+  <li>Eclipse BIRT Report Framework 2.0.</li>
+  <li>Eclipse BIRT RCP Report Designer 2.0.</li>
+  <li>Eclipse BIRT Runtime 2.0</li>
+  <li>Eclipse BIRT Charts 2.0</li>
+  <li>Eclipse BIRT Test Suites 2.0</li>
+</ul>
+
+<h2><a name="Milestones"></a>Release milestones</h2>
+<p>
+The Eclipse BIRT 2.0 release is targeted for release on December 30th 2005, 
+pending community release review. All release deliverables will be available 
+for download as soon as the release has been tested and validated in the 
+target operating configurations listed below.
+</p>
+
+<p>Release milestones:</p>
+<ul>
+  <li>Friday, September 16, 2005 BIRT 2.0 M1</li>
+  <li>Monday, October 24, 2005 BIRT 2.0 M2</li>
+  <li>Monday, November 21, 2005 BIRT 2.0 M3</li>
+  <li>Friday, December 30, 2005 BIRT 2.0 Release Candidate </li>
+  <li>Friday, January 20, 2006 BIRT 2.0</li>
+</ul>
+
+<p>
+For information about new features assigned to each milestone please refer to the 
+<a href="https://bugs.eclipse.org/bugs">bugzilla database</a>. The bugzilla database 
+will be updated on an ongoing basis as the plan progresses.
+</p>
+
+<h2><a name="TargetOperatingEnvironments"></a>Target Operating
+Environments</h2>
+
+<p>In order to remain current, each release of an Eclipse project targets
+reasonably current versions of underlying operating environments and other
+Eclipse projects on which it depends. </p>
+
+<p>
+Most of Eclipse, and all of BIRT, is &#8220;pure&#8221; Java&#8482; code and has no direct 
+dependence on the underlying operating system. For BIRT, the chief dependence 
+is on the Eclipse Platform, Graphical Editor Framework (GEF), Modeling 
+Framework (EMF), and on the Java 2 Platform that runs it. 
+</p>
+
+<p>The Eclipse BIRT 2.0 release depends on the following compatibility stack:</p>
+<b>BIRT 2.0 Reference Stack for Eclipse 3.1</b>
+<ul>
+  <li>Java 2 platform Java Development Kit (JDK) 1.4.2</li>
+  <li>Eclipse Platform Runtime Binary 3.1</li>
+  <li>Graphical Editor Framework (GEF) Runtime 3.1</li>
+  <li>Eclipse Modeling Framework (EMF) 2.1.0</li>
+</ul>
+<p>
+The Eclipse Platform and BIRT run in a variety of operating environments. Testing 
+is focused on a handful of popular <span class="header">combinations of operating system and Java 2 
+Platform; these are our <em>reference platforms</em>. Eclipse BIRT undoubtedly runs fine in 
+many operating environments beyond the reference platforms we test. However, since 
+we do not systematically test them we cannot vouch for them. Problems encountered 
+when running Eclipse BIRT on non-reference platforms that cannot be recreated on any 
+reference platform will be given lower priority than problems with running Eclipse 
+BIRT on a reference platform.</span></p>
+
+<p>For BIRT 2.0, the project team plans to tests and validate the following reference 
+platforms:</p>
+
+<table border="1">
+  <tbody>
+    <tr bgcolor="#CCCCCC">
+      <th colspan="4">
+        <div align="center">
+        <b><font size="+1">Eclipse BIRT Report Framework 2.0 and Eclipse BIRT RCP 
+Report Designer 2.0 Reference Platforms</font></b></div>
+      </th>
+    </tr>
+    <tr>
+      <td width="205"><b>Operating system</b></td>
+      <td width="76"><b>Processor architecture</b></td>
+      <td width="59"><b>Window system</b></td>
+      <td width="453"><b>Java 2 Platform</b></td>
+    </tr>
+    <tr>
+      <td width="205">Microsoft Windows XP</td>
+      <td width="76">Intel x86</td>
+      <td width="59">Win32</td>
+      <td width="453">Sun Java 2 Standard Edition, version 1.4.2, version 5.0</td>
+    </tr>
+    <tr>
+      <td width="205">Microsoft Windows 2000</td>
+      <td width="76">Intel x86</td>
+      <td width="59">Win32</td>
+      <td width="453">Sun Java 2 Standard Edition, version 1.4.2, version 5.0</td>
+    </tr>
+    <tr>
+      <td width="205">Microsoft Windows Server 2003</td>
+      <td width="76">Intel x86</td>
+      <td width="59">Win32</td>
+      <td width="453">Sun Java 2 Standard Edition, version 1.4.2, version 5.0</td>
+    </tr>
+    <tr>
+      <td width="205">Red Hat Enterprise Linux WS 3.0</td>
+      <td width="76">Intel x86</td>
+      <td width="59">GTK</td>
+      <td width="453">Sun Java 2 Standard Edition, version 1.4.2</td>
+    </tr>
+  </tbody>
+</table>
+
+<br>
+<table border="1">
+  <tbody>
+    <tr bgcolor="#CCCCCC">
+      <th colspan="4">
+        <div align="center">
+        <b><font size="+1">Eclipse BIRT Runtime 2.0 and Eclipse BIRT Charts 2.0 
+Reference Platforms</font></b></div>
+      </th>
+    </tr>
+    <tr>
+      <td width="205"><b>Operating system</b></td>
+      <td width="76"><b>Processor architecture</b></td>
+      <td width="59"><b>Window system</b></td>
+      <td width="453"><b>Java 2 Platform</b></td>
+    </tr>
+    <tr>
+      <td width="205">Microsoft Windows XP</td>
+      <td width="76">Intel x86</td>
+      <td width="59">Win32*</td>
+      <td width="453">Sun Java 2 Standard Edition, version 1.4.2</td>
+    </tr>
+    <tr>
+      <td width="205">Microsoft Windows XP</td>
+      <td width="76">Intel x86</td>
+      <td width="59">Win32*</td>
+      <td width="453">IBM SDK 1.4.2</td>
+    </tr>
+    <tr>
+      <td width="205">Microsoft Windows Server 2003</td>
+      <td width="76">Intel x86</td>
+      <td width="59">Win32*</td>
+      <td width="453">Sun Java 2 Standard Edition, version 1.4.2</td>
+    </tr>
+    <tr>
+      <td width="205">Microsoft Windows Server 2003</td>
+      <td width="76">Intel x86</td>
+      <td width="59">Win32*</td>
+      <td width="453">IBM SDK 1.4.2</td>
+    </tr>
+    <tr>
+      <td width="205">Red Hat Enterprise Linux WS 3.0</td>
+      <td width="76">Intel x86</td>
+      <td width="59">GTK*</td>
+      <td width="453">Sun Java 2 Standard Edition, version 1.4.2, BlackDown SDK 1.4.2</td>
+    </tr>
+    <tr>
+      <td width="205">SUSE Linux Enterprise Server 9</td>
+      <td width="76">Intel x86</td>
+      <td width="59">YaST*</td>
+      <td width="453">Sun Java 2 Standard Edition, version 1.4.2, BlackDown SDK 1.4.2</td>
+    </tr>
+  </tbody>
+</table>
+*Window system only required when displaying charts within SWT or SWING windows.<br>
+<br>
+<table border="1">
+  <tbody>
+    <tr bgcolor="#CCCCCC">
+      <th colspan="1">
+        <div align="center">
+        <b><font size="+1">BIRT Application Server Reference Platform</font></b></div>
+      </th>
+    </tr>
+    <tr>
+      <td width="405">Apache Tomcat 4.1.x, 5.5.x</td>
+    </tr>
+    <tr>
+      <td width="405">JBoss AS 4.0.2</td>
+    </tr>
+  </tbody>
+</table>
+<br>
+<table border="1">
+  <tbody>
+    <tr bgcolor="#CCCCCC">
+      <th colspan="1">
+        <div align="center">
+        <b><font size="+1">BIRT JDBC Reference Platforms</font></b></div>
+      </th>
+    </tr>
+    <tr>
+      <td width="405">MySQL Connector/J 3.x JDBC driver</td>
+    </tr>
+    <tr>
+      <td width="405">Derby V5.1 JDBC driver</td>
+    </tr>
+  </tbody>
+</table>
+<br>
+<table border="1">
+  <tbody>
+    <tr bgcolor="#CCCCCC">
+      <th colspan="1">
+        <div align="center">
+        <b><font size="+1">BIRT Browsers and Viewers Reference Platforms </font></b></div>
+      </th>
+    </tr>
+    <tr>
+      <td width="405">Mozilla Firefox 1.0</td>
+    </tr>
+    <tr>
+      <td width="405">Microsoft Internet Explorer 6.0</td>
+    </tr>
+    <tr>
+      <td width="405">Adobe Acrobat Reader 7.0</td>
+    </tr>
+  </tbody>
+</table>
+<br>
+<h4>Internationalization</h4>
+<p>Eclipse is designed as the basis for internationalized products. The user 
+interface elements provided by the various Eclipse projects, including dialogs 
+and error messages, are externalized. The English strings for BIRT are provided 
+as the default resource bundles. Translations are provided with this release 
+for French (fr_FR), German (de_DE), Spanish (es_ES), Japanese (ja_JP), Simplified 
+Chinese (zh_CN), and Korean (ko_KR).
+</p>
+
+<h2><a name="Compatibility"></a>Compatibility with Previous Releases</h2>
+
+<p>BIRT 2.0 will be compatible with earlier versions of BIRT to the greatest 
+extent possible. The nature and scope of some of the key plan items for BIRT 
+2.0 are such that the only feasible solutions might break compatibility. In 
+other regards, BIRT 2.0 will be compatible with 1.0.1 and 1.0. We also aim to 
+minimize the effort required to port an existing plug-in to the 2.0 APIs.
+</p>
+
+<h3>Compatibility of Release 2.0 with 1.x</h3>
+
+<p>BIRT 2.0 will be compatible with BIRT 1.x unless noted. The detailed 
+compatibility statement is listed below. In this statement, &quot;BIRT&quot; refers to 
+all BIRT components: BIRT Report Framework, BIRT Runtime, and BIRT Chart SDK.
+</p>
+
+<p><b>API Contract Compatibility:</b> BIRT 2.0 will be upwards contract-compatible 
+with BIRT 1.x to the greatest extent possible. All incompatibility exceptions will 
+be documented. Downward contract compatibility is not supported. There is no guarantee 
+that compliance with BIRT 2.0 APIs will ensure compliance with BIRT 1.x APIs. Refer 
+to general Eclipse document on 
+<a href="http://eclipse.org/eclipse/development/java-api-evolution.html">Evolving 
+APIs</a> for a discussion of the kinds of API changes that maintain contract compatibility.</p>
+
+<p>The BIRT Chart UI API v2.0 is not compatible with the v1.0 API due to a full redesign 
+of the Chart UI. However, older extension implementations are expected to be used with 
+the new version as noted below &#8211;</p>
+
+<u>Support for Old Chart UI Extension Points</u><br>
+<em>&#8216;uisheets&#8217; Extension Point: </em>The &#8216;uisheets&#8217; extension point will be supported
+but in a slightly limited form. It will be used to populate the navigation tree in the 
+formatting task sheet only. All extensions will be displayed under a special &#8216;Custom 
+Properties&#8217; node of the tree. The structure of the nodes represented by the extensions 
+will be maintained.<br><br>
+<em>&#8216;types&#8217; Extension Point: </em>This extension point will be supported with some new 
+functionality added to the interface. If the existing extension is created by 
+implementing the interface, it will need to be modified to implement the additional methods. 
+If it extends the default implementation, no changes will be needed. It will still be 
+suggested that the new functionality be reviewed so that its relevance to each extension 
+can be examined.<br><br>
+<em>&#8216;changelisteners&#8217; Extension Point: </em>This extension point will NOT be supported. 
+The functionality that could be extended and controlled using this extension point will 
+not be available in the new User Interface.<br><br>
+<em>&#8216;seriescomposites&#8217; Extension Point: </em>This extension point will be supported and 
+will have the same use as it did in version 1.0 viz. to provide UI components to set 
+attribute and data properties for custom series types. The location and use of these 
+custom composites however will be a little different in the new UI. In this case, the 
+data composite will be used in the data screen to allow setting of the data definition 
+for the series components. The attribute composite will be used in the advanced popup 
+for the series.
+
+<p><b>Binary (plug-in) Compatibility:</b> The BIRT 2.0 plug-in framework will be upwards 
+binary-compatible with BIRT 1.x plug-ins to the greatest extent possible. Downward 
+plug-in compatibility is not supported. Plug-ins for BIRT 2.0 will not be usable in BIRT 
+1.x. Extension plug-ins for BIRT 1.x will be upwards binary-compatible with BIRT 2.0.</p>
+
+<p><b>Source Compatibility:</b> BIRT 2.0 will be upwards source-compatible with BIRT 1.x to 
+the greatest extent possible. This means that source files written to use BIRT 1.x APIs 
+will successfully compile and run against BIRT 2.0 APIs. Downward source compatibility is 
+not supported. If source files use new BIRT APIs, they will not be usable with an earlier 
+version of BIRT.
+</p>
+
+<p><b>Report Design Compatibility:</b>BIRT 2.0 will be upwards report design 
+compatible with BIRT 1.x unless noted. This means that reports created with BIRT 
+1.x can be successfully opened by BIRT 2.0 and upgraded to a 2.0 format.
+</p>
+
+<p><b>Non-compliant usage of API's: </b> All non-API methods and classes, and certainly 
+everything in a package with &quot;internal&quot; in its name, are considered implementation 
+details which may vary between operating environment and are subject to change without 
+notice. Client plug-ins that directly depend on anything other than what is specified in 
+the BIRT API are inherently unsupportable and receive no guarantees about compatibility 
+within a single release much less with an earlier releases.</p>
+
+<h2><a name="Themes">Themes</a></h2>
+
+<p>
+Continuing on the theme for BIRT 1.x, the BIRT project's overriding release 2.0 theme 
+remains extending the Eclipse platform to provide infrastructure and tools that allow 
+application developers to design, deploy, generate and view reports within their 
+applications. In this context, the BIRT project also adopts and supports key themes 
+within the overall Eclipse planning process.
+</p>
+
+<ul>
+  <li><b>Scaling Up - </b>BIRT 2.0 targets the needs of report developers who report on 
+         large datasets generating large report documents with thousands of pages. This 
+         release also provides the capability to store report documents persistently.</li>
+  <li><b>Design for Extensibility - </b>BIRT 2.0 extends the extension points in the BIRT 
+         framework by implementing additional extensions on the framework. Some examples 
+         include support for XML as an additional data source and support for templates.</li>
+  <li><b>Simple to Use - </b>BIRT 2.0 includes a number of enhancements in this area such as 
+         scripting using Java, enhanced charting wizard functionality, improvements to the 
+         expression builder, and ease of use enhancements to the ROM API. Additionally, BIRT 
+         2.0 continues to provide the RCP based report designer which is targeted at the report 
+         developer.</li>
+  <li><b>Appeal to a Broader Community - </b>BIRT 2.0 will broaden the appeal of BIRT by enabling 
+         additional applications of BIRT technology. This will be made possible by the availability 
+         of support for numerous additional types of reports.</li>
+</ul>
+
+<h2><a name="Projects">Projects</a></h2>
+
+<h4>Report Types, Layouts, and Controls</h4>
+
+<blockquote>
+  <p><b>Multi-pass Aggregate, Sorting and Filtering</b>
+Some queries require multiple passes over the data. For example, a report may wish to display a 
+listing of top deals. The entry in the report for each deal might show the size of the deal as a 
+percentage of the total sales for that quarter. Such &#8220;two-pass&#8221; aggregates require BIRT to make 
+one pass over the data to compute the total for the quarter, then a second pass to generate the 
+report. This multi-pass aggregation is not supported by all data sources. This project therefore 
+extends BIRT to provide support for multi-pass aggregates for all data sources. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS2">BPS 2</a>][Bugzilla 
+ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110640">110640</a>][Theme: Simple to 
+use, Appeal to a Broader Community]</p>
+
+  <p><b>Top N / Bottom N Report Layout</b>
+Top N / Bottom N reports display information that is typically sorted by an aggregated number, for 
+example, a report that lists the top 3 performing sales people. This project will provide 
+capabilities to easily create a Top N / Bottom N type report section. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS2">BPS 2</a>][Bugzilla ID: 
+<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110641">110641</a>][Theme: Simple to use]</p>
+
+  <p><b>Provide support for binding Blob/Clob data to report controls</b>
+Many database  schemas, such as those used for call center or customer support applications,  contain columns defined as character large objects (CLOBs). These fields  contain, for example, the variable length and free format text notes that the  call center representative takes when speaking to a customer. <img src="/birt/project/new.gif" alt="New since last update to plan" width="12" height="12">In addition, an  human resources system might store pictures of employees in a database as  binary large objects (BLOBS). This project will provide easy support for  displaying BLOBS/CLOBs in a BIRT report. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS3">BPS 3</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110642">110642</a>][Theme: Simple to use, Appeal to a Broader Community]</blockquote>
+
+<h4>BIRT Java Script Objects</h4>
+<blockquote>  
+
+<p>BIRT 1.0 included support for many of the scripting object capabilities that are in JavaScript. 
+This project is intended to add more scripting objects. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS4">BPS 4</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110644">110644</a>][Theme: Simple to use]
+
+</blockquote>
+
+<h4>Interactive Report Viewing</h4>
+
+<blockquote>
+  <p><b>Page-on-Demand Navigation</b>
+Page-on-demand is a mechanism for dealing efficiently with large report documents over a 
+remote connection such as to the internet. Instead of reading an entire report into memory 
+or sending an entire report over a network, pages are requested by the application and sent 
+as needed. This method of data transfer improves response time for the end user and optimizes 
+resource usage. When integrating BIRT into applications, particularly web applications, 
+page-on-demand capabilities are needed to ensure that the application can be built with 
+acceptable performance. 
+
+This feature consists of two projects:
+1) providing the application developer with page-on-demand viewing API&#8217;s. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS22">BPS 22</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110645">110645</a>]
+2) including an exemplary implementation of a viewing framework that allows application 
+developers to easily integrate viewing functionality into their applications and customize 
+the viewing capabilities they choose. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS5">BPS 5</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110646">110646</a>]
+[Theme: Scaling up]
+
+
+<p><b>Report Paging</b>
+Long reports need to be divided into pages for effective use. This division can occur either 
+automatically, or with specific page breaks determined by the report developer. Multi-page 
+report support will allow the report developer to design reports that have controlled page 
+breaks (such as for each new group value), or using automatic page breaks, and for the 
+application developer to integrate page navigation of BIRT reports into the application itself. 
+The definition of a page in this context needs to be flexible to accommodate differing physical 
+characteristics, or logical constructs such as a page for each customer. This project enables 
+BIRT to support multi-page report output. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS19">BPS 19</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110671">110671</a>]
+[Theme: Scaling up]
+<p><b>Hyperlinks to Other Reports</b>
+This project provides the report developer the capability to link easily to another report while 
+not hard wiring the report to a particular environment. Additionally, if a user navigates to 
+another report, it also provides the mechanisms to retain the state of the original report. 
+[<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS5">BPS 5</a>][Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110648">110648</a>]
+[Theme: Simple to use]
+
+<p><b>Bookmarks (Hyperlinks into a Report Body)</b>
+It is often desirable to hyperlink into a specific point in a report document, for example, to 
+a chart that has sales summaries for the Western Region. Many report items can be the target of 
+hyperlinks. The BIRT bookmark feature is a string that uniquely identifies the item instance 
+within the report. This project provides support for the bookmark concept in BIRT reports. 
+[<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS5">BPS 5</a>][Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110651">110651</a>]
+[Theme: Simple to use]
+
+<p><b>Table of Contents Support in Viewer</b>
+A table of contents shows the hierarchical structure of a report to the end user and allows 
+the user to easily and quickly navigate to sections of the report. The hierarchy is defined by 
+the report grouping and sub report structure, with customizations possible by the report developer, 
+such as providing custom text for each node in the hierarchy. TOC features include: ability to 
+expand the TOC one level at a time, handle arbitrarily large groups at any node/level in the 
+hierarchy, and links from the group title jump to the first page of that group. Note that this 
+project is focused on TOC as a navigational mechanism in the report viewer, rather than providing a 
+TOC element that can be embedded in a report. This later item is a separate feature that is not 
+scheduled for this release. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS5">BPS 5</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110655">110655</a>]
+[Theme: Simple to use]
+</blockquote>
+
+<h4>Report Engine Scalability and Performance</h4>
+
+<blockquote>
+<p><b>Memory Usage Efficiency Improvement</b>
+This project intends to enhance the BIRT engine to utilize memory more efficiently. 
+[<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS6">BPS 6</a>][Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110656">110656</a>]
+[Theme: Scaling up]
+
+<p><b>Concurrent User Scalability Large Numbers of Active Users</b>
+When BIRT is deployed in a production environment with various kinds of application servers, it 
+is expected that there will be hundreds of users who concurrently need to run a BIRT report. 
+BIRT needs to be able to scale to handle running reports concurrently for large numbers of users. 
+[<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS6">BPS 6</a>][Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110658">110658</a>][Theme: Scaling up]
+
+</blockquote>
+
+<h4>Data Engine Scalability and Performance</h4>
+<blockquote>
+<p><b>Disk-Based Sorting and Data Manipulation</b>
+Reports against large data sets with millions of rows often require the report engine to sort the data and perform aggregation. To support these scenarios, this project incorporates a sorting and aggregation capability within the BIRT Engine, which, due to the potentially large data sets, can use a combination of memory and disk for the task. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS7">BPS 7</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110659">110659</a>]
+[Theme: Scaling up]
+
+<p><b>Cache Query Results while Developing</b>
+While designing a report, the developer specifies a data set to report on. If the number of 
+records in the data set is large, then the iterative process of making changes to a report 
+followed by previewing those changes slows down because the large data set has to be fetched 
+for each preview operation. This slowdown can hinder quick report design and adversely affect 
+the developer experience and productivity associated with BIRT. This project allows a report 
+developer to specify a property on a data set that limits the number of records that are 
+fetched during the development process, and that those results are cached as much as possible. 
+[<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS7">BPS 7</a>][Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110660">110660</a>][Theme: Simple to use]
+
+</blockquote>
+
+<h4>Report Document</h4>
+<blockquote>
+<p><b>Persistent Storage of Report Output</b>
+It is often desirable to run a report and then store the results of that report for viewing later. 
+For example, generating a large (1000s of pages) report and then viewing pages individually as 
+needed. To support this scenario, this project extends BIRT to offer a way to persistently save a 
+report for viewing at some point in the future. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS8">BPS 8</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110661">110661</a>][Theme: Scaling up]
+</blockquote>
+
+<h4><strong><img src="/birt/project/new.gif" alt="New since last update" width="12" height="12">Improved PDF Output  Generation </strong></h4>
+<blockquote>
+Robust PDF generation is a key component for reporting since many users generate PDF versions of the report for portability, printing and distribution. For BIRT, the PDF support needs to be very high quality. This project addresses issues related to PDF generation using FOP such as slow performance, limited support for lines and borders, and others. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS21">BPS 21</a>] [Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=120143">120143</a>][Theme: Scaling up]
+</blockquote>
+
+<h4><strong>Report Template</strong></h4>
+<blockquote>
+When creating a new report, BIRT provides the ability to select a template for the report design. 
+With BIRT 1.0, these templates are from a predefined list that is built into the user interface. 
+In order to support context specific uses of BIRT, the application developer wants to be able to 
+add new templates into the user interface. In addition, BIRT will allow templates to be added to 
+the user interface, and for cheat sheets to be associated with the template. It will also be 
+possible to include associations to a style sheet and/or library with the template design. This 
+would allow the developer to provide the person consuming the template with pre-defined styles 
+and/or visual components from a library. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS9">BPS 9</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110662">110662</a>][Theme: Design for extensibility]
+
+</blockquote>
+
+<h4>BIRT Library</h4>
+<blockquote>
+Libraries contain report components or functions for reuse in multiple report designs. A report 
+or library developer creates a library, then places it in a shared location for others to use. 
+Libraries improve developer productivity and promote report design consistency, and maintainability. 
+This project will provide library support within BIRT. This includes simple components and compound 
+compounds such as a page header with a logo and address. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS10">BPS 10</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110663">110663</a>]
+[Theme: Simple to use]
+
+</blockquote>
+
+<h4>BIRT Style and CSS Style Sheet</h4>
+<blockquote>
+<p><b>External Style Sheets for Use Across Multiple Report Designs</b>
+This project extends the concept of styles to allow the definition of a style to be contained in a 
+separate style sheet file that can be shared across multiple reports. This will make it easy to 
+establish a common look across all the reports in an application, and if needed, to be able to 
+quickly change the look across many reports just by editing the style sheet. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS11">BPS 11</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110746">110746</a>]
+[Theme: Scaling up, Simple to use]
+
+<p><b>Ability to import CSS Style Sheets</b>
+When designing a report that is going to be deployed in a corporate application, the developer of 
+the report should not have to recreate the styles that have already been defined for the look and 
+feel of the web site. This project allows the BIRT report developer to &quot;point&quot; to an existing CSS 
+style sheet file and import this for use within their report design to define various elements of 
+the report such as fonts, colors, and others. A future project will look at using a CSS style sheet 
+directly without the need to import. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS11">BPS 11</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110664">110664</a>]
+[Theme: Simple to use]
+
+</blockquote>
+
+<h4>Code Editor for BIRT Scripting</h4>
+<blockquote>
+BIRT supports the ability to script, or code, the behavior of reports in a number of ways. To 
+improve code editing, BIRT will leverage an Eclipse perspective for working with code in BIRT. 
+Perspectives exploit the power of Eclipse to the report designer&#8217;s benefit.  In addition, they 
+are a way to provide rich functionality by leveraging the Eclipse environment. This project will 
+provide support for and a perspective for Java Code Editing for BIRT reports. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS12">BPS 12</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110665">110665</a>]
+[Theme: Simple to use]
+
+</blockquote>
+
+<h4>Dynamic Parameter Selection List</h4>
+<blockquote>
+Parameterized BIRT reports can be used to provide a highly personalized experience. End-users 
+can choose to view the information that matters most to them when they want to see it. Parameter 
+values change as quickly as the business itself. For example, a sales manager may want to view 
+total sales closed by a particular salesperson. In order to support the more complex scenario, 
+BIRT should allow report developers to specify that the list of values for a parameter be 
+dynamically populated at run time. The goal of this project is to provide built-in support for 
+dynamic parameters. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS14">BPS 14</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110666">110666</a>]
+[Theme: Simple to use]
+
+</blockquote>
+
+<h4><img src="/birt/project/new.gif" alt="New since last update" width="12" height="12">Cascading Dynamic Parameter Lists</h4>
+<blockquote>
+Parameterized BIRT reports can be used to provide a highly personalized experience. Building on the support for Dynamic Parameter Lists, a report may require an end user, at run time, to specify more than 1 parameter that are cascaded together. For example, a regional sales report may require the user to specify parameters for the State and City. Suppose the user selects California for the state. The user may then want to see the sales information for a specific city. The user would then specify a value for the City parameter of the report. However, the values for the City parameter list would depend on the value selected for the State parameter and would dynamically at run time be populated with cities in California. This project concerns itself with providing the report developer with the ability to define dynamic parameters that are cascaded together as described above. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS14">BPS 14</a>][Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=120145">120145</a>][Theme: Simple to use]
+
+</blockquote>
+<h4>Chart Builder and Wizard</h4>
+<blockquote>
+BIRT includes support for including charts within a report design. The goal for this project 
+is to improve the usability of the chart control. We will be looking at both a Wizard/Builder 
+approach for common usage/charts, in addition to a more advanced capability for report 
+developers who want to control the chart in more detail. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS15">BPS 15</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110667">110667</a>]
+[Theme: Simple to use]
+
+</blockquote>
+
+<h4>Property Editor for Chart Report Item</h4>
+<blockquote>
+BIRT provides a Property Editor for accessing commonly used properties for visual and 
+non-visual components in a report. The Property Editor is not currently available for elements 
+in a chart within a report design. For consistency and developer productivity reasons, this 
+project aims to allow the Property Editor to be used for commonly changed properties in a 
+chart. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS16">BPS 16</a>][Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110668">110668</a>]
+[Theme: Simple to use]
+</blockquote>
+
+<h4>Chart component improvements</h4>
+<blockquote>
+This project looks at the charting component of BIRT to make a number of significant improvements 
+in chart specification and generation. Examples of improvements to be made include, the ability 
+to use report styles in charts, handling the situation when labels on the X-axis overlap, 
+specifying a legend title, or marker shapes. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS17">BPS 17</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110669">110669</a>]
+[Theme: Simple to use]
+</blockquote>
+
+<h4>Scripting of Charts</h4>
+<blockquote>
+Some Report developers will want to customize the behavior of a chart in a report to meet 
+specific needs requested by their end users. For example, to highlight specific visual elements 
+in a chart based on data values such as expanding the pie slice for the median data value. This 
+project will provide the ability within BIRT to control the behavior of a chart with methods on 
+the chart control. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS18">BPS 18</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110670">110670</a>]
+[Theme: Simple to use]
+</blockquote>
+
+<h4>Expression  Builder</h4>
+<blockquote>
+With the Expression Builder in BIRT 1.0, it is awkward to build the expression using the user 
+interface. There are a number of improvements that can be made to make it easier to navigate 
+around the functions, and to provide the user with help on each of the functions that are 
+available. This project implements those usability improvements. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS20">BPS 20</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110672">110672</a>]
+[Theme: Simple to use]
+</blockquote>
+
+<h4><img src="/birt/project/new.gif" alt="New since last update" width="12" height="12">View/Edit XML Report Designs</h4>
+<blockquote>
+For developers working with report designs visually in the Layout View, it is useful to be able to see the XML associated with the report design they are working on. With BIRT 1.0, it is only possible to see the XML report design if you close the visual editor and open the design file in the Eclipse XML editor. In BIRT 1.0, it was not possible to easily switch between the visual and XML view. This project provides a mechanism for the report developer to easily switch between the visual and XML views of a report design, and to be able to edit the report in either view.[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=120923">120923</a>][Theme: Simple to use]
+</blockquote>
+
+<h4>XML Data Sources</h4>
+<blockquote>
+With the rapid adoption of XML as the lingua franca for business information exchange, and for 
+the exchange of information within an application, a large number of developers would like to 
+report against XML data sources. Additionally, most ERP and CRM applications now provide 
+interfaces to deliver data in XML. This project provides an out of the box adapter to access 
+XML data sources. This can be used &quot;as is&quot; or as an example ODA connector that can be adapted 
+for other purposes. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS23">BPS 23</a>]]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110673">110763</a>]
+[Theme: Simple to use, Appeal to a Broader Community]
+</blockquote>
+
+<h4>Dataset parameters</h4>
+<blockquote>
+Certain data sources, such as those accessing data in RDBMS's, support the concept of stored 
+procedures and functions. These constructs provide the capability to pass in parameters as well as 
+pass out resulting data values. This project concerns itself with building the capability to access 
+the output parameters from these types of constructs via BIRT scripting capability. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS24">BPS 24</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110765">110765</a>]
+[Theme: Simple to use, Appeal to a Broader Community]
+</blockquote>
+
+<h4>Report Object Model API</h4>
+<blockquote>
+The BIRT Design Engine API allows developers to programmatically manipulate a report design using 
+an API, rather than manipulating the XML directly. This API was introduced in BIRT 1.0 and is used 
+extensively within the BIRT project itself. This project makes some enhancements to the Design 
+Engine API based on feedback from the community and the BIRT project&#8217;s own use of the API. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS29">BPS 29</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110676">110676</a>]
+[Theme: Design for extensibility]
+</blockquote>
+
+<h4>ODA framework migration to DTP</h4>
+<blockquote>
+<p><b>Move ODA Runtime Extension Point and Java Interfaces to DTP</b> The ODA Runtime Extension Point 
+and Java Interface components will be part of the Eclipse Data Tools Project (DTP) going forward. 
+This BIRT project will move these components from the BIRT areas of Eclipse to DTP and make any 
+naming changes as needed. This includes reviewing and removing any BIRT project dependency and 
+allowing this to use the DTP project instead. The BIRT project team members originally working on 
+this component will continue to work on this project within the DTP project. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS30">BPS 30</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110677">110677</a>]
+[Theme: Design for extensibility]
+
+<p><b>Provide Plug-in Adapter for BIRT ODA Drivers to DTP ODA</b>
+The ODA Runtime Extension Point and Java Interface components will be part of the Eclipse Data Tools 
+Project (DTP) going forward. All ODA Consumer applications are expected to upgrade and adopt the DTP 
+ODA framework and namespace in lieu of the BIRT ODA namespace. For compatibility with existing 
+adapters, this project will provide a plug-in adapter for BIRT ODA drivers that implement the BIRT 
+ODA 2.0.x interfaces. This will allow a DTP ODA consumer application to consume existing BIRT ODA 
+data providers without any source code or binary build changes.  However, if an ODA data provider 
+wants to implement any of the enhancements added to ODA version 3.0 or later, its implementation 
+must migrate and adopt the DTP ODA interfaces. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS30">BPS 30</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110678">110678</a>]
+[Theme: Design for extensibility]
+</blockquote>
+
+<h4>Export Report Data</h4>
+<blockquote>
+<p><b>Data Extraction from a Saved Report</b>
+This project supports data extraction from a report at several different levels: 1) Report 
+level 2) Dataset level 3) Report item level for a table, list, or chart items 4) Report item 
+instance. Extraction at the report level can be achieved by repeatedly retrieving data for each 
+dataset. Extraction at the report item instance level would include computed columns as normal 
+columns. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS32">BPS 32</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110679">110679</a>]
+[Theme: Simple to use, Appeal to a Broader Community]
+
+<p><b>Ability to Export Report Data as CSV</b>
+Building on the infrastructure of exporting data from a report, this project allows the end user 
+to extract report data as a CSV formatted file. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS32">BPS 32</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110680">110680</a>]
+[Theme: Simple to use, Appeal to a Broader Community]
+</blockquote>
+
+<h4>Pass-through of external context objects</h4>
+<blockquote>
+The BIRT engine is often embedded as part of a middle-tier application server, where the BIRT 
+components are added to the mix of various J2EE components. During report run-time, some of these 
+other components may instantiate context objects, which are served to the BIRT engine for its custom 
+data source to use. The BIRT engine will thus need to pass through such external Java objects into 
+the BIRT data source components for consumption. These context objects are assumed to be dynamically 
+instantiated at report run-time, and are not statically defined in a report design. The scope of this 
+project thus focuses on data source specific run-time Java objects which are instantiated external to 
+BIRT, and are passed through to a custom data source provider plugged in the BIRT engine. Some 
+examples of the types of external context objects that may be passed through to a BIRT data source 
+provider include, an open JDBC connection, a pooled connection, user authorization keys, or query 
+parameter values collected outside of BIRT. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS35">BPS 35</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110682">110682</a>]
+[Theme: Design for extensibility]
+</blockquote>
+
+<h2><a name="Defects">Defects</a></h2>
+BIRT 2.0 will address defects reported by project members and the community. The 
+<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=BIRT&target_milestone=2.0.0+Final&target_milestone=2.0.0+M1&target_milestone=2.0.0+M2&target_milestone=2.0.0+M3&target_milestone=2.0.0+M4&tar">list of defects</a> 
+targeted for resolution in BIRT 2.0 can be found in the bugzilla database on 
+<a href="https://bugs.eclipse.org/bugs">https://bugs.eclipse.org/bugs</a>.
+
+</body>
+</html>
+
+
+</body>
+</html>
+
diff --git a/project/project_plan_R2_0_0_Draft.html b/project/project_plan_R2_0_0_Draft.html
index 092a346..9fb6a5d 100644
--- a/project/project_plan_R2_0_0_Draft.html
+++ b/project/project_plan_R2_0_0_Draft.html
@@ -11,7 +11,7 @@
 <body>
 
 <p class="head">BIRT Project DRAFT 2.0 Plan</p>
-<p class="subhead">Last revised 28 September, 2005</p>
+<p class="subhead">Last revised 9 December, 2005 (<img src="/birt/project/new.gif" alt="New since last update" width="12" height="12"> marks interesting changes since the previous draft of 28 September, 2005) </p>
 
 
 <h2><a name="Introduction"></a>Introduction</h2><p>
@@ -81,8 +81,8 @@
   <li>Friday, September 16, 2005 BIRT 2.0 M1</li>
   <li>Monday, October 24, 2005 BIRT 2.0 M2</li>
   <li>Monday, November 21, 2005 BIRT 2.0 M3</li>
-  <li>Monday, December 5, 2005 BIRT 2.0 Release Candidate</li>
-  <li>Friday, December 30, 2005 BIRT 2.0</li>
+  <li>Friday, December 30, 2005 BIRT 2.0 Release Candidate </li>
+  <li>Friday, January 20, 2006 BIRT 2.0</li>
 </ul>
 
 <p>
@@ -411,13 +411,8 @@
 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110641">110641</a>][Theme: Simple to use]</p>
 
   <p><b>Provide support for binding Blob/Clob data to report controls</b>
-Many database schemas, such as those used for call center or customer support applications, contain 
-columns defined as character large objects (CLOBs). These fields contain, for example, the variable 
-length and free format text notes that the call center representative takes when speaking to a 
-customer. This project will provide easy support for displaying CLOBs in a BIRT report. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS3">BPS 3</a>]
-[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110642">110642</a>][Theme: Simple to use, Appeal to a Broader Community]
-
-</blockquote>
+Many database  schemas, such as those used for call center or customer support applications,  contain columns defined as character large objects (CLOBs). These fields  contain, for example, the variable length and free format text notes that the  call center representative takes when speaking to a customer. <img src="new.gif" alt="New since last update to plan" width="12" height="12">In addition, an  human resources system might store pictures of employees in a database as  binary large objects (BLOBS). This project will provide easy support for  displaying BLOBS/CLOBs in a BIRT report. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS3">BPS 3</a>]
+[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110642">110642</a>][Theme: Simple to use, Appeal to a Broader Community]</blockquote>
 
 <h4>BIRT Java Script Objects</h4>
 <blockquote>  
@@ -460,8 +455,7 @@
 characteristics, or logical constructs such as a page for each customer. This project enables 
 BIRT to support multi-page report output. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS19">BPS 19</a>]
 [Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110671">110671</a>]
-[Theme: Scaling up]<br>
-
+[Theme: Scaling up]
 <p><b>Hyperlinks to Other Reports</b>
 This project provides the report developer the capability to link easily to another report while 
 not hard wiring the report to a particular environment. Additionally, if a user navigates to 
@@ -477,21 +471,6 @@
 [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS5">BPS 5</a>][Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110651">110651</a>]
 [Theme: Simple to use]
 
-<p><b>Progressive Viewing</b>
-When a report is large, generating the report could take a long time. It is not efficient or user 
-friendly to require a user to wait until the whole report is generated before viewing the first 
-page. Progressive viewing allows a user to view the first few pages of a report while the remaining 
-pages are still being generated. This provides a web application with acceptable performance.
-
-This feature consists of two projects:
-1) Providing APIs for the application developer to progressively generate and view a report. 
-[<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS22">BPS 22</a>][Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110652">110652</a>]
-2) Including an exemplary implementation of a viewing framework that allows application developers 
-to easily integrate viewing functionality into their applications and customize the viewing 
-capabilities they choose. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS5">BPS5</a>]
-[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110654">110654</a>]
-[Theme: Scaling up]
-
 <p><b>Table of Contents Support in Viewer</b>
 A table of contents shows the hierarchical structure of a report to the end user and allows 
 the user to easily and quickly navigate to sections of the report. The hierarchy is defined by 
@@ -504,7 +483,6 @@
 scheduled for this release. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS5">BPS 5</a>]
 [Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110655">110655</a>]
 [Theme: Simple to use]
-
 </blockquote>
 
 <h4>Report Engine Scalability and Performance</h4>
@@ -552,7 +530,12 @@
 [Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110661">110661</a>][Theme: Scaling up]
 </blockquote>
 
-<h4>Report Template</h4>
+<h4><strong><img src="new.gif" alt="New since last update" width="12" height="12">Improved PDF Output  Generation </strong></h4>
+<blockquote>
+Robust PDF generation is a key component for reporting since many users generate PDF versions of the report for portability, printing and distribution. For BIRT, the PDF support needs to be very high quality. This project addresses issues related to PDF generation using FOP such as slow performance, limited support for lines and borders, and others. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS21">BPS 21</a>] [Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=120143">120143</a>][Theme: Scaling up]
+</blockquote>
+
+<h4><strong>Report Template</strong></h4>
 <blockquote>
 When creating a new report, BIRT provides the ability to select a template for the report design. 
 With BIRT 1.0, these templates are from a predefined list that is built into the user interface. 
@@ -626,6 +609,11 @@
 
 </blockquote>
 
+<h4><img src="new.gif" alt="New since last update" width="12" height="12">Cascading Dynamic Parameter Lists</h4>
+<blockquote>
+Parameterized BIRT reports can be used to provide a highly personalized experience. Building on the support for Dynamic Parameter Lists, a report may require an end user, at run time, to specify more than 1 parameter that are cascaded together. For example, a regional sales report may require the user to specify parameters for the State and City. Suppose the user selects California for the state. The user may then want to see the sales information for a specific city. The user would then specify a value for the City parameter of the report. However, the values for the City parameter list would depend on the value selected for the State parameter and would dynamically at run time be populated with cities in California. This project concerns itself with providing the report developer with the ability to define dynamic parameters that are cascaded together as described above. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS14">BPS 14</a>][Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=120145">120145</a>][Theme: Simple to use]
+
+</blockquote>
 <h4>Chart Builder and Wizard</h4>
 <blockquote>
 BIRT includes support for including charts within a report design. The goal for this project 
@@ -752,18 +740,6 @@
 [Theme: Simple to use, Appeal to a Broader Community]
 </blockquote>
 
-<h4>Reportlet</h4>
-<blockquote>
-Web pages often use HTML tables instead to organize and position their content. In order to provide 
-more flexibility for integrating report content into the customer&#8217; web pages, it becomes necessary 
-to introduce a new set of formats that return content as &#8220;Reportlets&#8221; or partial DHTML pages.  These 
-reportlets can then be included within web pages generated by the customer&#8217;s web application. This 
-project focuses on producing content that is easily embeddable within an overall HTML page. [<a href="http://www.eclipse.org/birt/wiki/index.php?n=BPS.BPS34">BPS 34</a>]
-[Bugzilla ID: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110681">110681</a>]
-[Theme: Simple to use, Appeal to a Broader Community]
-
-</blockquote>
-
 <h4>Pass-through of external context objects</h4>
 <blockquote>
 The BIRT engine is often embedded as part of a middle-tier application server, where the BIRT 
diff --git a/release20specs/APIChangeControlDocuments/ODA30_API_Changes_SPEC.pdf b/release20specs/APIChangeControlDocuments/ODA30_API_Changes_SPEC.pdf
index 58e5f8b..65a15a7 100644
--- a/release20specs/APIChangeControlDocuments/ODA30_API_Changes_SPEC.pdf
+++ b/release20specs/APIChangeControlDocuments/ODA30_API_Changes_SPEC.pdf
Binary files differ
diff --git a/release20specs/BIRT Engine API Change Control Document.pdf b/release20specs/BIRT Engine API Change Control Document.pdf
deleted file mode 100644
index 1092bb9..0000000
--- a/release20specs/BIRT Engine API Change Control Document.pdf
+++ /dev/null
Binary files differ
diff --git a/release20specs/BPS15 1.0.1 Charts_UI_Extensibility.pdf b/release20specs/BPS15 1.0.1 Charts_UI_Extensibility.pdf
deleted file mode 100644
index 6a0c40b..0000000
--- a/release20specs/BPS15 1.0.1 Charts_UI_Extensibility.pdf
+++ /dev/null
Binary files differ
diff --git a/release20specs/BPS17 - Chart Components SPEC.pdf b/release20specs/BPS17 - Chart Components SPEC.pdf
index c0d77f1..795b55b 100644
--- a/release20specs/BPS17 - Chart Components SPEC.pdf
+++ b/release20specs/BPS17 - Chart Components SPEC.pdf
Binary files differ
diff --git a/release20specs/BPS18 - Chart Scripting SPEC.pdf b/release20specs/BPS18 - Chart Scripting SPEC.pdf
deleted file mode 100644
index 0e9971d..0000000
--- a/release20specs/BPS18 - Chart Scripting SPEC.pdf
+++ /dev/null
Binary files differ
diff --git a/release20specs/BPS20_ExpressionBuilderSpec.pdf b/release20specs/BPS20_ExpressionBuilderSpec.pdf
deleted file mode 100644
index 3c0b9b0..0000000
--- a/release20specs/BPS20_ExpressionBuilderSpec.pdf
+++ /dev/null
Binary files differ
diff --git a/release20specs/BPS22 Page-On-Demand Viewing.pdf b/release20specs/BPS22 Page-On-Demand Viewing.pdf
index 206b1c6..c648851 100644
--- a/release20specs/BPS22 Page-On-Demand Viewing.pdf
+++ b/release20specs/BPS22 Page-On-Demand Viewing.pdf
Binary files differ
diff --git a/release20specs/BPS27 BIRT Deployment.pdf b/release20specs/BPS27 BIRT Deployment.pdf
deleted file mode 100644
index 5f2728b..0000000
--- a/release20specs/BPS27 BIRT Deployment.pdf
+++ /dev/null
Binary files differ
diff --git a/release20specs/BPS28_Report Layout Manager.pdf b/release20specs/BPS28_Report Layout Manager.pdf
deleted file mode 100644
index fcec2c6..0000000
--- a/release20specs/BPS28_Report Layout Manager.pdf
+++ /dev/null
Binary files differ
diff --git a/release20specs/BPS35_ODAPassThruContext_SPEC.pdf b/release20specs/BPS35_ODAPassThruContext_SPEC.pdf
index 95ec943..f68303f 100644
--- a/release20specs/BPS35_ODAPassThruContext_SPEC.pdf
+++ b/release20specs/BPS35_ODAPassThruContext_SPEC.pdf
Binary files differ
diff --git a/release20specs/BPS37 - Chart Interactivity SPEC.pdf b/release20specs/BPS37 - Chart Interactivity SPEC.pdf
index a13de8d..3026aa2 100644
--- a/release20specs/BPS37 - Chart Interactivity SPEC.pdf
+++ b/release20specs/BPS37 - Chart Interactivity SPEC.pdf
Binary files differ
diff --git a/release20specs/BPS38 - Chart Types SPEC.pdf b/release20specs/BPS38 - Chart Types SPEC.pdf
index a634392..8c87fb7 100644
--- a/release20specs/BPS38 - Chart Types SPEC.pdf
+++ b/release20specs/BPS38 - Chart Types SPEC.pdf
Binary files differ
diff --git a/release20specs/BPS39/BPS39 1.0.1 - Chart Engine Extensibility.pdf b/release20specs/BPS39/BPS39 1.0.1 - Chart Engine Extensibility.pdf
deleted file mode 100644
index c00f894..0000000
--- a/release20specs/BPS39/BPS39 1.0.1 - Chart Engine Extensibility.pdf
+++ /dev/null
Binary files differ
diff --git a/release20specs/BPS39/BPS39 1.0.1 - Chart Engine Usage and Integration.pdf b/release20specs/BPS39/BPS39 1.0.1 - Chart Engine Usage and Integration.pdf
deleted file mode 100644
index d681fde..0000000
--- a/release20specs/BPS39/BPS39 1.0.1 - Chart Engine Usage and Integration.pdf
+++ /dev/null
Binary files differ
diff --git a/tutorial/basic/customers.rptdesign b/tutorial/basic/customers.rptdesign
index 593c48b..bd302f8 100644
--- a/tutorial/basic/customers.rptdesign
+++ b/tutorial/basic/customers.rptdesign
@@ -1,51 +1,48 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Written by Eclipse BIRT 1.0 -->
-<report xmlns=" http://www.eclipse.org/birt/2005/design" version="1">
+<report xmlns="http://www.eclipse.org/birt/2005/design" version="3" id="1">
     <property name="createdBy">Eclipse BIRT Designer Version 1.0.0 Build &lt;20050405-1230></property>
     <property name="units">in</property>
     <data-sources>
-        <oda-data-source name="Sample">
-            <property name="driverName">sampledb</property>
-        </oda-data-source>
+        <oda-data-source extensionID="org.eclipse.birt.report.data.oda.sampledb" name="Sample" id="11"/>
     </data-sources>
     <data-sets>
-        <oda-data-set name="Customers">
+        <oda-data-set extensionID="org.eclipse.birt.report.data.oda.jdbc.JdbcSelectDataSet" name="Customers" id="12">
             <property name="dataSource">Sample</property>
             <property name="queryText">SELECT *
 FROM CUSTOMERS
 WHERE COUNTRY = 'USA'</property>
-            <property name="type">JdbcSelectDataSet</property>
         </oda-data-set>
     </data-sets>
     <styles>
-        <style name="report">
+        <style name="report" id="2">
             <property name="fontFamily">sans-serif</property>
         </style>
-        <style name="label"/>
-        <style name="text"/>
-        <style name="data"/>
-        <style name="table"/>
-        <style name="grid"/>
-        <style name="list"/>
-        <style name="image"/>
-        <style name="Header">
+        <style name="label" id="3"/>
+        <style name="text" id="4"/>
+        <style name="data" id="5"/>
+        <style name="table" id="6"/>
+        <style name="grid" id="7"/>
+        <style name="list" id="8"/>
+        <style name="image" id="9"/>
+        <style name="Header" id="10">
             <property name="backgroundColor">#0080FF</property>
             <property name="fontWeight">bold</property>
             <property name="color">#FFFFFF</property>
         </style>
     </styles>
     <page-setup>
-        <simple-master-page name="Simple MasterPage">
+        <simple-master-page name="Simple MasterPage" id="13">
             <page-header>
-                <grid>
+                <grid id="14">
                     <property name="width">100%</property>
-                    <column/>
-                    <row>
-                        <cell>
+                    <column id="15"/>
+                    <row id="16">
+                        <cell id="17">
                             <property name="fontSize">xx-large</property>
                             <property name="fontWeight">bold</property>
                             <property name="textAlign">center</property>
-                            <text>
+                            <text id="18">
                                 <text-property name="content"><![CDATA[Title]]></text-property>
                             </text>
                         </cell>
@@ -53,20 +50,20 @@
                 </grid>
             </page-header>
             <page-footer>
-                <grid>
+                <grid id="19">
                     <property name="width">100%</property>
-                    <column/>
-                    <column/>
-                    <row>
-                        <cell>
-                            <text>
+                    <column id="20"/>
+                    <column id="21"/>
+                    <row id="22">
+                        <cell id="23">
+                            <text id="24">
                                 <property name="contentType">html</property>
                                 <text-property name="content"><![CDATA[<value-of>new Date()</value-of>]]></text-property>
                             </text>
                         </cell>
-                        <cell>
+                        <cell id="25">
                             <property name="textAlign">right</property>
-                            <text>
+                            <text id="26">
                                 <text-property name="content"><![CDATA[Page:]]></text-property>
                             </text>
                         </cell>
@@ -76,29 +73,29 @@
         </simple-master-page>
     </page-setup>
     <body>
-        <grid>
+        <grid id="27">
             <property name="width">100%</property>
-            <column>
+            <column id="28">
                 <property name="width">33%</property>
             </column>
-            <column>
+            <column id="29">
                 <property name="width">33%</property>
                 <property name="textAlign">center</property>
             </column>
-            <column>
+            <column id="30">
                 <property name="width">33%</property>
                 <property name="textAlign">right</property>
             </column>
-            <row>
+            <row id="31">
                 <property name="verticalAlign">top</property>
-                <cell>
-                    <image>
-                        <expression name="uri">http://www.eclipse.org/birt/tutorial/multichip-4.jpg</expression>
+                <cell id="32">
+                    <image id="33">
+                        <expression name="uri">"http://www.eclipse.org/birt/tutorial/basic/multichip-4.jpg"</expression>
                     </image>
                 </cell>
-                <cell>
+                <cell id="34">
                     <property name="verticalAlign">top</property>
-                    <text>
+                    <text id="35">
                         <property name="contentType">html</property>
                         <text-property name="content"><![CDATA[<CENTER>
 <FONT size="6" color=blue>
@@ -109,9 +106,9 @@
 </CENTER>]]></text-property>
                     </text>
                 </cell>
-                <cell>
+                <cell id="36">
                     <property name="verticalAlign">top</property>
-                    <data>
+                    <data id="37">
                         <structure name="dateTimeFormat">
                             <property name="category">Long Date</property>
                             <property name="pattern">Long Date</property>
@@ -120,14 +117,14 @@
                     </data>
                 </cell>
             </row>
-            <row>
+            <row id="38">
                 <property name="height">0.25in</property>
-                <cell/>
-                <cell/>
-                <cell/>
+                <cell id="39"/>
+                <cell id="40"/>
+                <cell id="41"/>
             </row>
         </grid>
-        <table name="table1">
+        <table name="table1" id="42">
             <property name="borderBottomColor">#000000</property>
             <property name="borderBottomStyle">solid</property>
             <property name="borderBottomWidth">medium</property>
@@ -147,110 +144,110 @@
                     <expression name="key">row["CUSTOMERNAME"]</expression>
                 </structure>
             </list-property>
-            <column>
+            <column id="88">
                 <property name="width">1.208in</property>
             </column>
-            <column>
+            <column id="89">
                 <property name="width">1.197in</property>
             </column>
-            <column>
+            <column id="90">
                 <property name="width">2.114in</property>
             </column>
-            <column>
+            <column id="91">
                 <property name="width">1.635in</property>
             </column>
             <header>
-                <row>
-                    <cell>
-                        <label>
+                <row id="43">
+                    <cell id="44">
+                        <label id="45">
                             <property name="style">Header</property>
                             <text-property name="text">State</text-property>
                         </label>
                     </cell>
-                    <cell>
-                        <label>
+                    <cell id="46">
+                        <label id="47">
                             <property name="style">Header</property>
                             <text-property name="text">City</text-property>
                         </label>
                     </cell>
-                    <cell>
-                        <label>
+                    <cell id="48">
+                        <label id="49">
                             <property name="style">Header</property>
                             <text-property name="text">Name</text-property>
                         </label>
                     </cell>
-                    <cell>
-                        <label>
+                    <cell id="50">
+                        <label id="51">
                             <property name="style">Header</property>
                             <text-property name="text">Phone</text-property>
                         </label>
                     </cell>
                 </row>
             </header>
-            <group>
+            <group id="52">
                 <expression name="keyExpr">row["STATE"]</expression>
                 <header>
-                    <row>
+                    <row id="53">
                         <property name="backgroundColor">#BBDDFF</property>
-                        <cell>
-                            <data>
+                        <cell id="54">
+                            <data id="55">
                                 <property name="fontSize">large</property>
                                 <property name="fontWeight">bold</property>
                                 <expression name="valueExpr">row["STATE"]</expression>
                             </data>
                         </cell>
-                        <cell/>
-                        <cell/>
-                        <cell/>
+                        <cell id="56"/>
+                        <cell id="57"/>
+                        <cell id="58"/>
                     </row>
                 </header>
                 <footer>
-                    <row>
-                        <cell/>
-                        <cell/>
-                        <cell/>
-                        <cell/>
+                    <row id="59">
+                        <cell id="60"/>
+                        <cell id="61"/>
+                        <cell id="62"/>
+                        <cell id="63"/>
                     </row>
                 </footer>
             </group>
-            <group>
+            <group id="64">
                 <property name="interval">none</property>
                 <property name="sortDirection">asc</property>
                 <expression name="keyExpr">row["CITY"]</expression>
                 <header>
-                    <row>
-                        <cell/>
-                        <cell>
-                            <data>
+                    <row id="65">
+                        <cell id="66"/>
+                        <cell id="67">
+                            <data id="68">
                                 <property name="fontSize">large</property>
                                 <property name="color">#0080FF</property>
                                 <expression name="valueExpr">row["CITY"]</expression>
                             </data>
                         </cell>
-                        <cell/>
-                        <cell/>
+                        <cell id="69"/>
+                        <cell id="70"/>
                     </row>
                 </header>
                 <footer>
-                    <row>
-                        <cell/>
-                        <cell/>
-                        <cell/>
-                        <cell/>
+                    <row id="71">
+                        <cell id="72"/>
+                        <cell id="73"/>
+                        <cell id="74"/>
+                        <cell id="75"/>
                     </row>
                 </footer>
             </group>
             <detail>
-                <row>
-                    <cell/>
-                    <cell/>
-                    <cell>
-                        <data>
+                <row id="76">
+                    <cell id="77"/>
+                    <cell id="78"/>
+                    <cell id="79">
+                        <data id="80">
                             <expression name="valueExpr">row["CUSTOMERNAME"]</expression>
                         </data>
                     </cell>
-                    <cell>
-                        <data>
+                    <cell id="81">
+                        <data id="82">
                             <structure name="stringFormat">
                                 <property name="category">Custom</property>
                                 <property name="pattern">(@@@)@@@-@@@@</property>
@@ -261,11 +258,11 @@
                 </row>
             </detail>
             <footer>
-                <row>
-                    <cell/>
-                    <cell/>
-                    <cell/>
-                    <cell/>
+                <row id="83">
+                    <cell id="84"/>
+                    <cell id="85"/>
+                    <cell id="86"/>
+                    <cell id="87"/>
                 </row>
             </footer>
         </table>
diff --git a/whatsnew.html b/whatsnew.html
index 6fa0d8d..0884268 100644
--- a/whatsnew.html
+++ b/whatsnew.html
@@ -9,10 +9,30 @@
 <p class="head">BIRT Project</p>
 <p class="subhead">What's New</p>
 
+<h1>2006</h1>
+
+<dl class="date-list">
+<dt>January 22</dt>
+<dd><a href="http://download.eclipse.org/birt/downloads">BIRT 2.0</a>
+is now available for download.  Read about the feature set at <a href="project/notable2.0.html">Notable Features - BIRT 2.0</a> </dd>
+
+<dt>January 16</dt>
+<dd><a href="http://www.eclipse.org/birt/index.php?page=project/pmc.html">The BIRT PMC</a> is pleased to announce 
+that Mike Fox, from IBM / Rational, has joined the Committee.</dd>
+
+<dt>January 4</dt>
+<dd><a href="http://download.eclipse.org/birt/downloads">BIRT 2.0 Release Candidate</a>
+is available for download.</dd>
+</dl>
+
 <h1>2005</h1>
 
 <dl class="date-list">
 
+<dt>December 7</dt>
+<dd><a href="http://download.eclipse.org/birt/downloads">BIRT 2.0 Milestone 3</a>
+can now be downloaded.  Read about the feature set at <a href="project/notable2.0M3.html">Notable Features - BIRT 2.0 M3</a> </dd>
+
 <dt>November 3</dt>
 <dd><a href="http://download.eclipse.org/birt/downloads/examples/misc/BIRT/BIRT_demo_Camv3.html" target="_blank" class="top">A new BIRT Demo</a> is available for viewing.</dd>
 
diff --git a/wiki/cookbook/comments.php b/wiki/cookbook/comments.php
index 8a88ddc..e16aa11 100644
--- a/wiki/cookbook/comments.php
+++ b/wiki/cookbook/comments.php
@@ -34,7 +34,7 @@
 

 // feel free to choose :)

 # InitComments();

-InitCommentsStyled();

+# InitCommentsStyled();

 

 // Initializes $RecentComments array.

 if( !isset($RecentComments) ) {

@@ -46,7 +46,7 @@
 }

 

 // thought it'd be better here

-BasicCommentSetup();

+#BasicCommentSetup();

 

 // Initializes structures with plain content

 function InitComments() {

@@ -79,7 +79,7 @@
 		<input type='submit' name='delete' value=' $[Delete] ' onclick='javascript:text.value=\"\";' />

 		<input type='button' value=' $[Reset] ' onclick='javascript:text.value=\"\"; uid.value=\"0\"'/>

 	");

-	SDV($CommentsFooterFmt, "wiki:$[PmWiki.CommentsFooter]");

+	SDV($CommentsFooterFmt, "wiki:$[PmWikiFooter]");

 }

 

 // Initializes structures with styled content

@@ -112,7 +112,7 @@
 		<input type='submit' name='delete' value=' $[Delete] ' onclick='javascript:text.value=\"\";' />

 		<input type='button' value=' $[Reset] ' onclick='javascript:text.value=\"\"; uid.value=\"0\"'/>

 	");

-	SDV($CommentsFooterFmt, "wiki:$[PmWiki.CommentsFooter]");

+	SDV($CommentsFooterFmt, "wiki:$[PmWikiFooter]");

 }

 

 // aquires special params (uid & text) and initializes buttons.

@@ -206,7 +206,7 @@
 // Then do so :)

 function CommentsFileName($pagename) {

 	global $WorkDir;

-	return $WorkDir.'/'.$pagename.".Comments";

+	return $WorkDir.'/'.$pagename."Save";

 }

 // Creates/updates/deletes comments

 function HandlePostComment( $pagename ) {