how to deal with patches?

[Carter Bullard]

Gentle people,
   We have a patch for argus that fixes two problems,
one with a Vlan tag information error that mangles the
argus record, and a tiny little problem reading MOAT
packets (generating erroneous "Fragment extension buffer
not found" errors).

   How would you guys like to handle these patches?
Do they represent unstable release 2.0.1 code, or simple
patches for 2.0.0?  Should patches go out immediately
and managed in a separate area on the web site?
Should I mail patches to the argus mailing list automatically?
Should I go ahead and release 2.0.1?  How about
argus-2.0.1.beta.1a?  .... Just kidding ;o)

   I personally would like to avoid putting out minor
version releases every week, so I'd like to either put
up patches for those that are having problems, and then
have a release with all the patches rolled up, possibly
every 8 weeks or so.

   This of course is just an opinion, does anyone have a
suggestion as to how to handle patches and minor version
releases?


Thanks!!!

Carter

Carter Bullard
QoSient, LLC
300 E. 56th Street, Suite 18K
New York, New York  10022

carter at qosient.com
Phone +1 212 588-9133
Fax   +1 212 588-9134
http://qosient.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20010403/151041a5/attachment.html>