Argus 3.0 release status

[Carter Bullard]

Gentle people,
So we've been at this argus-3.0 thing for quite a while now, and I think
its time to release this thing we call argus.  The work is not over  
after
its let "out of the bag" so to speak, but the demand for fixes  
etc.... can
be pretty bad if the basics aren't covered at the beginning.

Argus is quite stable, and with this last fix, its been used and  
stressed
on quite a number of machines, architectures, etc, so I think we're good
to go with the probe.

The clients are in good shape, but possibly just in good shape.
I think as long as we have ra, racluster, radium, rasplit, rastream,
racount, rahisto, ranonymize, rapolicy, rasort, rastrip, ragrep and
ratop, we should be in business.  (seems like a lot to stay in
business)

There is an outstanding issue with rastrip() that I am working right  
now,
and in some ways it is related to the problem with rasplit()'s
"stime is zero" issue, so hopefully that bug will be squashed this
weekend.

There is an outstanding issue with ratop(), which I will also have
addressed in the short term, as I have people screaming at me
regarding the last set of changes, so that is going to be addressed.

Any other issues?  Please speak up now, or forever hold your peace!!!

Documentation is still an issue, but I believe that we have the basics,
but I would like to hear from the group opinions and comments.
Sanity checks are always good, especially when your sanity is in
question ;o)

All of you have put in a lot of time and effort into a project that is
dominated by my approach to building software (which is not
something to emulate by the way), and I very much appreciate your
patience.    I think argus-3.0 has been a good project, and I hope
all of you are getting something out of it that is useful for you!!!

Thanks again, and hopefully soon, we'll have an official release!!!!!

Carter