1.1.2 bug, news lists

[craig at jcb-sc dot com]

Jeff and others, before we get too closed-down on the 1.1.2 front,
could y'all make sure we'll ship it with good pointers to live
information on the web pages regarding bugs and news?

I mean, I think there have been a lot of improvements made in just
the past week or two.

But, I want us to take the time to ensure that 1.1.2 itself points
to information that we can easily keep up-to-date with regard to
newly discovered bugs (post-1.1.2-ship).

In particular, Jeff, the cgi-bin/fortrannews and cgi-bin/fortranbugs
scripts (which I can't find in my checked-out copy of wwwdocs, FWIW)
seem *nearly* ready for prime-time, and I'd like them to replace
the fortran.html stuff I recently updated by hand-tweaking the
outputs of texi2html over bugs.texi and news.texi.

So, I'm thinking there shouldn't be any equivalent to fortran.html
in the egcs-1.1.2 info on the web page -- though there should be a
link to the new bugs/news info that's automatically generated.

But, I don't know how to do that (link up stuff like that).  I could
experiment, break things, and generally annoy people, of course, but
that seems counterproductive.  :)

If you can deal with the general issues above, including replacing
the fortran.html stuff with pointers to the bug info, that'd be great.

What I'm especially interested in seeing is the top-level egcs page
contain two items:

  We try to provide late-breaking information on *known bugs*, and
  *news* about items already planned for upcoming releases.

The known-bugs link would point to that new bugs.html file, which
then would, I think, need a heading for Fortran (and some editorial
fix-ups, e.g. to the titlage), which would contain a link to your
automatically-produced fortranbugs thingy.  (Or something like that.)
Other languages might still want their news hand-coded into this
file, as they shouldn't have to also provide bugs.texi and news.texi
files like g77 has (for so long now).

As far as fixing things so fortranbugs and fortrannews properly
honor @ifhtml and @ifnothtml -- right now, fortranbugs starts off
looking pretty silly, in the middle of a sentence, apparently
due to this -- let me know if I can help.  I'm a bit of a toolsmith,
though I don't think I have the sources to things like texi2html
handy.  (E.g. if you want me to write a quicky pre-filter for it,
or something, I could do that.  Not sure which language would be
appropriate, though, and I don't know Perl yet.)

        tq vm, (burley)