How do I...

Target Milestones in Openoffice.org

"Target Milestone" shows the OOo version, in which a RESOLUTION for the problem in the issue should be included. The contents of the "Target Milestone" can be changed by QA member of developers. For FIXED issue the developer/QA member will set the content of the "Target Milestone" to the version where the fix will be included. The issue will be verified before integration to the "Target Milestone" codeline. Once the fix has been confirmed as integrated on this "Target Milestone" the issue can be closed.
For more details see the OpenOffice.org Roadmap and the Q-concept document.

Target Milestone (OOo Later) for future release (2.x/3.0/???).

Features which have no dedicated resources for the next release according to the Program Concept document .
Default for new Enhancements.

Target Milestone (OOo 2.0) for next release (2.0).

Feature according to Program Concept document Resources for fixing and QA should already been allocated or assigned. The 2.0 codeline has been declared as "feature complete" in November 2004.
Defects with Prio 1 or 2.

Target Milestone ( OOo 2.0.1) for future bugfix release (2.0.x)

Issues that will not meet March timeline for final 2.0 release.

Target Milestone (OOo 1.1.5) for current bugfix release (1.1.x).

only to be set if issues are of major priority (P1/P2 or major regression to 1.0.x release) and can be fixed. Also patches for ports and localizations will be accepted. Resources for fixing and QA should already been allocated or fix is already available.
Appoval of Release Committee is required.

Target Milestone (OOo PleaseHelp)

Tasks which have no assigned resources for any release yet. Help for those issues is wanted, everybody is invited to look for issues to implement. Once a volunteer for implementation has been found the target milestone will be adjusted to one of the "real life" target described above according to OpenOffice.org Roadmap.

$Date: 2005/01/10 14:08:10 $