🚀 go-pugleaf

X
    Well, the long-awaited XELOS arrived yesterday.  There's a
lot of documentation, (19 small binders) which appears fairly well done.
Since we're a production machine, we can't just shut down and bring
it up.  That and conversion of our programs will have to await the
week-ends of the coming month.  If XELOS has all the stuff in it
that it claims (and it works) it should be real nice.

    Ok, people - CONFESS!! - pe.cust.bugs has been fairly quiet
recently.  What bugs have people found in XELOS???  If no one has
played with it too much, maybe no one knows.  If someone at one
of the regional pe* sites would like to be a repository for XELOS
bug reports, that would be fine.  Preferably someone with source,
who could look into fixing them. (hint, hint, earlw).  If no one 
at P-E has time to do this, I would be glad to.  I can't do 
anything about the bugs, as we're only  a binary site, but I'd 
be glad to listen.  I would suggest we  keep a running list of bugs, 
who sent in a SCR on them, and when.   In this way, we may be able 
to get a jump on things and form a much more coherent body of 
knowledge about Xelos than we have about Edition VII.

    What say ye voices of the net?

P.S. Am I missing something?  We're only getting about one
message per day in the pe.cust.* groups.  If this is indeed
an accurate measure of the traffic, why do we have all these
subgroups?  Why wouldn't pe.cust be adequate?  Or do we 
envision a great and mighty future?

-- 
            Brent Laminack  (akgua!itm!brent)