🚀 go-pugleaf

[Apologies if you saw my earlier cross-posting to comp.lang.fortran,
gnu.announce, and gnu.misc.discuss -- I couldn't find it, so assumed it
was lost.]

I am posting this message regarding the info-gnu-fortran mailing list
because it should by now be populated with the email addresses of pretty
much everyone who has indicated interest in being on the list.  The list
includes people who want to be alpha and beta testers as well as those who
are interested in future efforts towards implementing Fortran 90.  (My
earlier postings to comp.lang.fortran and email interactions suggested
that I'd try to keep separate lists, but I've been told this isn't really
necessary or desired by the administrators of GNU lists.)

I'd like to send out a reasonably complete status update soon.  In fact
I wanted to last summer, but the FSF machines and their mailers were
undergoing rapid change and I was asked to hold off until later (and
with my vacation/trip schedule, that became much later).

Before I send out the update, I'd first like to let everyone on this list
know that they indeed are on the list.  I've sent a message to the list that
takes care of that.  If you received it, you are on the list, so you don't
need to send a message to ask to be added to it.  On the other hand, if you
want to be removed from the list, send a request to the address shown
below.

After a week or so for everyone to get on or off the list as they choose,
I'll send out a status update, including what I hope to be a reasonably
accurate projection for when I want to start alpha testing and what I'd
like alpha testing to accomplish (in summary: shake out the front end,
since that's the hardest part, and deal with the backend issues like
how well Fortran code is optimized during beta or later).  I'd like to
include a list of features supported beyond ANSI FORTRAN 77, but that might
have to wait until a subsequent notice.

As far as the purpose of info-gnu-fortran@gnu.ai.mit.edu, I guess the idea
is that it is a forum for communicating information on the status and
capabilities of GNU Fortran, not so much discussing whether GNU Fortran
should have this or that feature or what bugs that are found in it once
testing begins.  I'm a neophyte at these mailing list things, so please
bear with me if I'm wrong about this.  I'd like to see a GNU Fortran
list (or better yet, newsgroup) form once testing begins, but that depends
on the demand for such a thing, apparently.  I'm sure there'll be a need
for a bug-gnu-fortran@gnu.ai.mit.edu mailing list once testing begins (but
of course they'll all be backend bugs :-).

So, if you want to add, delete, or change your email name relative to the
info-gnu-fortran@gnu.ai.mit.edu mailing list, send your request to:

    info-gnu-fortran-request@gnu.ai.mit.edu

If you have important, can't-wait-for-it kinds of questions or comments,
I guess you can send them to me, burley@gnu.ai.mit.edu, but keep in mind
that time I spend answering questions directly impacts the release schedule
of GNU Fortran, so I'd rather answer such questions after alpha testing
begins.  (Comments about my tendency to profusely post on various newsgroups
will be ignored. :-)

Also, I think it is not necessary to start making a list of those who wish
to be alpha testers, especially since I'm not even sure alpha testing will
happen as a phase distinct from beta testing.  When I get close to having
something testable, I'll put out the appropriate queries.  So if you want
to be an alpha or beta tester, it is enough for now just to be on the
mailing list.

--

James Craig Burley, Software Craftsperson    burley@gnu.ai.mit.edu