<html><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8"><link type="text/css" href="www/default_style.css" rel="stylesheet"><link type="text/css" href="www/webtools/wtp.css" rel="stylesheet"><title>Web Tools 1.5 Release Plans</title></head><body><table border="0" cellpadding="2" cellspacing="5" width="100%"><tbody><tr><td align="left" width="60%"><font class="indextop">wtp 1.5 release plans</font><br><font class="indexsub">Web Tools 1.5 Release Plans</font></td><td width="40%"><img src="www/images/wtplogosmall.jpg" align="middle" height="129" hspace="50" width="207"></td></tr></tbody></table><table border="0" cellpadding="2" cellspacing="5" width="100%"><col width="16"><col width="*"><tbody><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">Introduction</font></b></td></tr><tr><td align="right" valign="top"> </td><td valign="top"><p> | |
WTP is divided into components and uses a milestone-based | |
development process. Detailed release planning is done for | |
each component and milestone. | |
</p></td></tr><tr><td align="right" valign="top"> </td><td valign="top"><p> | |
The releases plans for WTP 1.5 are maintained in following | |
places: | |
</p></td></tr><tr><td align="right" valign="top"> </td><td valign="top"><ul> | |
<li> | |
<a href="#Bugzilla">Bugzilla</a> | |
</li> | |
<li> | |
<a href="#Milestone-Plans">Milestone Plans</a> | |
</li> | |
<li> | |
<a href="#Test-Plans">Test Plans</a> | |
</li> | |
</ul></td></tr><tr><td align="right" valign="top"> </td><td valign="top"><p> | |
Bugzilla is the definitive source of information about work | |
items that are planned for a release. Bugzilla is used to | |
manage defects and enhancements - both are referred to as | |
bugs. | |
</p></td></tr><tr><td align="right" valign="top"> </td><td valign="top"><p> | |
Although Bugzilla maintains much useful information, it is | |
not a suitable way to record detailed design information or | |
work plans. We therefore use milestone plan documents to | |
record additional information about bugs. The information in | |
milestone plan documents should be consistent with that in | |
Bugzilla. Finally, we use test plan documents to describe | |
the testing activities for the release. | |
</p></td></tr><tr><td align="right" valign="top"> </td><td valign="top"><p> | |
The relation between Bugzilla and the milestone plans is | |
described in the following document: | |
</p></td></tr><tr><td align="right" valign="top"><img src="www/images/Adarrow.gif" border="0" height="16" width="16"></td><td><a href="bugzilla-milestone-plans.html">Bugzilla and Milestones Plans</a></td></tr><tr><td align="right" valign="top"> </td><td valign="top"><br></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica"> | |
<a name="Bugzilla"></a> | |
Bugzilla | |
</font></b></td></tr><tr><td align="right" valign="top"> </td><td valign="top"><p> | |
The user interface of Bugzilla can be used directly to | |
search for the bugs in a given component and milestone. In | |
addition, the Web site includes reports that list all the | |
bugs for a given component and milestone, and links them to | |
corresponding items in the milestone plan documents. Any | |
inconsistencies between the bug and the corresponding | |
milestone plan document are included in the report. | |
</p></td></tr><tr><td align="right" valign="top"> </td><td valign="top"><p> | |
The bug list reports for each component and milestone are | |
listed in the following index: | |
</p></td></tr><tr><td align="right" valign="top"><img src="www/images/Adarrow.gif" border="0" height="16" width="16"></td><td> | |
<a href="buglist-report-index.html"> | |
Bug List Report Index | |
</a> | |
</td></tr><tr><td align="right" valign="top"> </td><td valign="top"><br></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica"> | |
<a name="Milestone-Plans"></a> | |
Milestone Plans | |
</font></b></td></tr><tr><td align="right" valign="top"> </td><td valign="top"><p> | |
The milestone plans for each component and milestone are | |
listed in the following index: | |
</p></td></tr><tr><td align="right" valign="top"><img src="www/images/Adarrow.gif" border="0" height="16" width="16"></td><td><a href="milestone-plan-index.html">Milestone Plan Index</a></td></tr><tr><td align="right" valign="top"> </td><td valign="top"><p> | |
The work items for the current and future milestones are | |
summarized in the following overview report: | |
</p></td></tr><tr><td align="right" valign="top"><img src="www/images/Adarrow.gif" border="0" height="16" width="16"></td><td> | |
<a href="reports/report-milestone-overview.html"> | |
Milestone Plan Overview | |
</a> | |
</td></tr><tr><td align="right" valign="top"> </td><td valign="top"><p> | |
The work items that need help are summarized in the | |
following help wanted report: | |
</p></td></tr><tr><td align="right" valign="top"><img src="www/images/Adarrow.gif" border="0" height="16" width="16"></td><td> | |
<a href="reports/help-wanted.html">Help Wanted Listing</a> | |
</td></tr><tr><td align="right" valign="top"> </td><td valign="top"><br></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica"> | |
<a name="Test-Plans"></a> | |
Test Plans | |
</font></b></td></tr><tr><td align="right" valign="top"> </td><td valign="top"><p> | |
The test plans for each component and milestone are listed | |
in the following index: | |
</p></td></tr><tr><td align="right" valign="top"><img src="www/images/Adarrow.gif" border="0" height="16" width="16"></td><td><a href="test-plan-index.html">Test Plan Index</a></td></tr></tbody></table></body></html> |