I write software which is used internally at my company. My internal
customers "qualify" my software before using it. We've had this discussion.
Frequent releases require frequent "quals" on their part. At the very least,
frequent re-installs. This is typically on hundreds of systems. What we
settled on is to group bug fixes and other "do-do" items into chunks that
last no less than about a month of development time. This works out good. We
make an exception for serious or "show-stopper" bugs.

Bruce

> -----Original Message-----
> From: Jim Menard [mailto:jimm / eris.io.com]
> Sent: Thursday, March 08, 2001 7:40 AM
> To: ruby-talk / ruby-lang.org; ruby-talk / netlab.co.jp
> Subject: [ruby-talk:12273] [ANN] NQXML v0.3.0 fixes DOCTYPE bug
> 
> 
> NQXML version 0.3.0 is now available. From the README file:
> 
>     Version 0.3.0 fixes a DOCTYPE tag bug (PUBLIC and SYSTEM 
> id arguments
>     were parsed incorrectly), adds some XML well-formedness 
> constraints,
>     adds access to input line numbers, improves some error 
> messages, and
>     starts the code documentation process.
> 
> As usual, NQXML is available from the RAA or the NQXML home page at
> http://www.io.com/~jimm/downloads/nqxml/.
> 
> A question for the group: are my frequent releases and 
> announcements useful
> or annoying? I want to release early and often, but I don't 
> want to make
> enemies.
> 
> Jim
> -- 
> Jim Menard, jimm / io.com, http://www.io.com/~jimm/
> "Hey, wait a minute. You've got both eyes! You're no special agent.
> You're just some jerk who hates my mustache!" - The Tick
>