From hww3@riverweb.com Sun Sep 5 20:56:38 1999
Date: Sun, 05 Sep 1999 20:43:51 -500
From: hww3@riverweb.com
To: ivend@riverweb.com
Bcc: hwellive@harris.com
Subject: iVend Update

[ The following text is in the "iso-8859-1" character set. ]
[ Your display is set for the "US-ASCII" character set. ]
[ Some characters may be displayed incorrectly. ]

Greetings!

I'm writing to let you know about a few new developments in the iVend world:

1. Anonymous Read-Only CVS access

In order to allow easy access to the latest iVend code fixes, I've set up an anonymous CVS server. You may access the latest code by installing CVS on your system and issuing the following commands:

cvs -d :pserver:anonymous@bay.riverweb.com:/cvs login

when prompted for a password, use "cvs". Then, run the following command:

cvs -d :pserver:anonymous@bay.riverweb.com:/cvs checkout ivend

And after some messages displayed to the screen, you should have a copy of the latest snapshot of iVend.

To update your source after the initial checkout, you'd run the following command from within the ivend/ directory:

cvs -d :pserver:anonymous@bay.riverweb.com:/cvs update

As a side note, this service runs in a chroot'ed environment that is updated from the master repository every 15 minutes.

2. Bugzilla

I've also set up Bugzilla for reporting and tracking bugs in iVend. You may access the iVend Bugzilla system by pointing your web browser at the following address:

http://hww3.riverweb.com/bugzilla/

>From there you may report bugs and query the status of existing bugs. This will allow you and I to keep track of what bugs have been reported and squashed.

I encourage everyone to use this system, as it allows me to keep better track of what problems are occurring with iVend.

When reporting a bug, I ask that you provide the following information:

a. The output of the command "uname -a".
b. Your version of Roxen, for example, 1.2.70.
c. The version of iVend, for example 1.0.34 or snapshot taken 091099.
d. Any backtrace generated, and/or the relevant portions of your default.1 debug log.
e. Any relevant information that may help to track the problem, such as steps you performed just before the error occurred, if you feel they're relevant.

By providing this information to me right away, I can more easily figure out the root cause and get a resolution to the problem more quickly.

3. What's coming up...

I plan to have a new beta release ready this week. Some of the new features include:

a. Less bugs
b. More documentation
c. Online payment proccessing through Signio (PaymentNet)
d. Spell Check in the product/group administration interface.

Stay tuned, because lots more is on the way.

As always, if you have comments or suggestions, please feel free to contact me at the address below.

Best Regards,

Bill
--
Bill Welliver
hww3@riverweb.com