That would be Changes.txt I believe....
> * Access to the latest version of Emerald, beta or otherwise. If it is
> beta, then there is an explicit note saying that you should only use this
> software at your own risk.
I figure if you download something from a folder called BETA you would be
smart enough to figure that out on your own....
> * A bug submission page that needs to be filled out with required
details
> (version number, problem, type of access server, etc). Will also have a
> note on the page asking to check out the current list of bugs before
> submitting one.
I think this list works great as that... then everyone can try it out and
see if its a problem with them... like a giant super-variant computer farm
to test emermald out on....
> * A feature list, which features will be implemented in which versions,
> what these features actually do in rough detail.
>
> Anything else??
>
> Alot of the time, we get really irritated because we don't know what to
> expect of other people or what people expect of us. By getting a rock
solid
> list of things we expect, the programmers/support at IEA will not over
> stress themselves trying to live up to presumed expectations.
>
> We also have no grounds to hassle Dale about what we expect because
we've
> just stated what we expect. In hard copy. Evidence he can shove in our
> faces whenever someone tries to hustle something extra.
>
>
--------------------------------------#------------------------------------
> David Khoury | "Where's the KABOOM ??
> Technical Manager & Comms Engineer | There was supposed to be an
> dave@flex.com.au | earth shattering KABOOM!!"
> http://www.flex.com.au/~dave | Marvin the Martian
>
--------------------------------------#------------------------------------
>
>
> ----------------------------------------------------------
> Emerald Mailing List listserver@emerald.iea.com