Tracking a release with dozens of languages and several platforms can be tedious. This is especially the case if the only used tool is a manually maintained table with colors indicating the status.
A web based tool should help us to keep track of the location and status of the builds as well as the responsible contact. The workflow in place should be supported. The tool should provide an overview, the means to maintain a release including easy status manipulations.
* firstname.lastname@example.org * Andre Schnabel (Andre.Schnabel at gmx.net)
Official QA'ing of contributed builds
From other locales or lesser known ports
* email@example.com or firstname.lastname@example.org * Kevin Hendricks (khendricks at openoffice.org)
More formal regression testing
* email@example.com * Kevin Hendricks (khendricks at openoffice.org)
Bug Tracking System statistics
Provide statistics issues submitted per time, number of active contributors, etc
* firstname.lastname@example.org * Martin Hollmichel (mh at openoffice.org)