special thanks to
for the xsl and ant scripts and
for original ideas.
Abstract:
This document proposes the format of New features plans and describes how they
can be used.
Changes:
May 22, 2001
The original proposal for review
May 28, 2001
Updated after nbdev comments
Contents:
Overview
Features per module
XSL styles
Generated html files
Strenghts and Weaknesses
1. Overview
The reson of this proposal is to simplify the work with new features
proposals in NetBeans. It will allow to write xsl files, which will generate the
exact collection of features you need (e.g. only significant features for the
whole release). An example can be the generation of "WhatIsNew.html"
file at the end of release cycle.
The features will be collected per module in one features.xml file.
Using xsl it is possible to generate html files for every module and also
features for whole release. It will be possible to track the implementation
progress during the implementation phase.
2. Features per module
The new features for upcoming releases are organized per module.
Each proposal is formated in xml.
The file is stored in the same place for every module: $module/www/plans/features.xml
2.1 Features.xml overview
The features.xml files contain requirements. Every requirement must
have:
Name
Description
Target milestone (3.3, 3.4, etc.)
Priority ("Must have", "Should have",
"Nice to have")
Optional (but recommended) part contains:
One or more responsible persons (with e-mails)
Links (e.g. links to Issuezilla enhancement, link to separate html
file which describes the feature, ...)
Percentage of completion (this will allow everyone to track, how many features
are already implemented)
Duration (the amount of the work - in days per developer)
2.2 Features.xml format
The format of features.xml file is as simple as possible.
