On 6 Dec 2004, at 00:03, Phil Steitz wrote:
snip
Also, what exactly is the purpose of README.html in
http://www.apache.org/dist/jakarta/commons/foo and why are these files
not in cvs? Some components have this file and some do not. It is
referred to in section 11 of
psteitz 2004/12/05 15:19:11
Removed: math STATUS.html
Log:
Removed STATUS file obsoleted by project.xml, changes.xml
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
This is actually a precedent-setting commit. ;-)
Currently, the Commons charter states that a status file must exist,
and, to date, I believe people have assumed that that file must be
named either STATUS.txt or STATUS.html. Since, as Phil says below,
this status file is obsoleted by the
Martin Cooper wrote:
This is actually a precedent-setting commit. ;-)
No -- [dbcp], [codec], [launcher] and [pool] all show dead STATUS.html
files in cvs attic. Several others - [configuration], [betwixt], [cli],
[net] do not appear to have ever had a STATUS file.
Currently, the Commons charter
I also dropped RELEASE-NOTES.txt and was planning to include a link in
README.html and on the commons download page to the changes.html
generated by maven, similarly to what [configuration] does.
Is that OK, or should I add this file back, putting the links to the
maven-generated report in the
On Sun, 05 Dec 2004 17:54:38 -0500, Phil Steitz [EMAIL PROTECTED] wrote:
Martin Cooper wrote:
This is actually a precedent-setting commit. ;-)
No -- [dbcp], [codec], [launcher] and [pool] all show dead STATUS.html
files in cvs attic. Several others - [configuration], [betwixt], [cli],
Currently, the Commons charter states that a status file must exist,
and, to date, I believe people have assumed that that file must be
named either STATUS.txt or STATUS.html. Since, as Phil says below,
this status file is obsoleted by the combination of project.xml and
changes.xml, at least for
