| <?xml version="1.0" encoding="UTF-8"?> |
| <?xml-stylesheet type="text/xsl" href="stylesheets/wtp.xsl"?> |
| |
| <html> |
| <head> |
| <title>Web Tools 1.0 Release Plans</title> |
| <meta content="www" name="root" /> |
| </head> |
| <body> |
| <h1>wtp 1.0 release plans</h1> |
| <h2>Introduction</h2> |
| |
| <p> |
| WTP is divided into components and uses a milestone-based |
| development process. Detailed release planning is done for |
| each component and milestone. |
| </p> |
| |
| <p> |
| The releases plans for WTP 1.0 are maintained in following |
| places: |
| </p> |
| <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> |
| <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> |
| |
| <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> |
| |
| <p> |
| The relation between Bugzilla and the milestone plans is |
| described in the following document: |
| </p> |
| |
| <h3><a href="bugzilla-milestone-plans.html">Bugzilla and Milestones Plans</a></h3> |
| <br /> |
| |
| <h2> |
| <a name="Bugzilla" /> |
| Bugzilla |
| </h2> |
| |
| <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> |
| |
| <p> |
| The bug list reports for each component and milestone are |
| listed in the following index: |
| </p> |
| |
| <h3> |
| <a href="buglist-report-index.html"> |
| Bug List Report Index |
| </a> |
| </h3> |
| <br /> |
| |
| <h2> |
| <a name="Milestone-Plans" /> |
| Milestone Plans |
| </h2> |
| <p> |
| The milestone plans for each component and milestone are |
| listed in the following index: |
| </p> |
| |
| <h3><a href="milestone-plan-index.html">Milestone Plan Index</a></h3> |
| |
| <p> |
| The work items for the current and future milestones are |
| summarized in the following overview report: |
| </p> |
| <h3> |
| <a href="reports/report-milestone-overview.html"> |
| Milestone Plan Overview |
| </a> |
| </h3> |
| <p> |
| The work items that need help are summarized in the |
| following help wanted report: |
| </p> |
| <h3> |
| <a href="reports/help-wanted.html">Help Wanted Listing</a> |
| </h3> |
| |
| <br /> |
| |
| <h2> |
| <a name="Test-Plans" /> |
| Test Plans |
| </h2> |
| <p> |
| The test plans for each component and milestone are listed |
| in the following index: |
| </p> |
| <h3><a href="test-plan-index.html">Test Plan Index</a></h3> |
| |
| </body> |
| </html> |
