Not delivering {bugs,gnats,faq}.html in releases

[Joseph S. Myers]

On Thu, 26 Jun 2003, Gerald Pfeifer wrote:

> I had a look, and transforming this into something that is really suitable
> for someone without web access (there is a lot of "useless"  stuff there)

s/without web access/without web access to gcc.gnu.org at that time/.  I
observed the following failure mode of web bug submission last night:

* Log in to Bugzilla, prepare bug report.
* Try to submit, and find that gcc.gnu.org has gone down since the bug
report form was retrieved.
* So need to cut and paste bug report into a file for later submission.

(Mail is more robust at queuing data when some link in the transmission
chain is down.  A point not I think mentioned in the previous discussions
of why people prefer gccbug (offline usage, using a real text editor, ...).)

> > Removing documentation previously present in releases of how to use part
> > of those releases would certainly be a regression.
> 
> Aren't we talking only about the documentation of (Bugzilla) components
> here?

I think essentially so.

(One thing that should be done to the _online_ form - which was a problem
with GNATSweb, and is still a problem with Bugzilla - is pointing out to
users that they should change the component from the default "ada" if it
isn't an Ada bug - some manage to miss this.  Or making the default "---"  
and only accepting the form if a non-default value has been entered.)

-- 
Joseph S. Myers
jsm28@cam.ac.uk