Rick Hillegas wrote:
Hi Jean,
Thanks for researching this. I have to admit that a flat STATUS file
seems like a fairly inexpressive way to track important facts. I'd vote
for some subversion-controlled webpages linked from the top level
website.(just as
http://db.apache.org/derby/derby_downloads.html#How+to+build+Derby links
to BUILDING.txt).
I should point out that derby_downloads.html links to
code/trunk/BUILDING.txt -- and that currently there is a BUILDING.txt in
every branch.
Just *one* file should describe status. There's really no reason it
couldn't even be a flat text or html file in the main derby directory in
svn (I see some ASF projects put readme files and the like at that level).
If it's outside the derby/site directory then every committer would be
able to update it without any knowledge of how to build the derby web
site with forrest, and there would be no publish step on people.apache.org.
If we want an approach more integrated with the web site, like OJB (
http://db.apache.org/ojb/status.html ) and Torque (
http://db.apache.org/torque/status.html ), then we would need to include
the page in derby/site. We could still keep the format in simple html so
any committer could commit changes, then let those who know how to build
the site publish the change.
While I'm on the topic, I also have to admit that the shifting contents
of the STATUS file confuse me. For example, at one point, I thought that
STATUS was supposed to track all the votes we've taken--but now I see
that STATUS only tracks recent votes.
Probably the confusion was a side effect of derby muddling its way
through incubation with two forms of tracking status. :-)
-jean
