Andrew McIntyre wrote:
On 1/4/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote:
At any rate, Derby can certainly have a STATUS file (and some ASF
projects do), but I wanted to mention that is isn't required. There
might be better ways to track and publish project status.
The DB project guidelines state that the projects should keep release
plans and decisions made in a status file:
http://db.apache.org/decisions.html
But maybe that page is out of date?
I think that's an exhortation to maintain a status somewhere -- not
necessarily in a flat file in the source code tree named "status" or
"STATUS".
Since Derby has a STATUS file in every code branch, we don't really have
a single go-to spot that tracks status for the project as a whole.
Torque and OJB maintain status in a web page:
http://db.apache.org/torque/status.html
http://db.apache.org/ojb/status.html
I think each project can decide itself how to maintain status.
If we want to put one on the derby web site like Torque and OJB do, I'd
recommend simple html format so that all committers can easily update it.
-jean
