I disagree. The most useful method of timing releases for both developers and users Is when the features reach critical mass. That way it is worth the effort for the developers to release and the users to upgrade.
Edgar > The real underlying problem, which we should address in post 1.1, is > that our releases have become too coarsely grained. Moving past 1.1, we > should try to release whenever a significant feature is added, rather > than when the features reach some critical mass. > -Ted. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
