tag:blogger.com,1999:blog-13831777.post-43921330920898792002008-01-02T18:50:00.000-05:002008-01-02T18:50:00.000-05:00Melbournian,<BR/><BR/>You bring up a good point! Releasing frequently is a tool. It won't make sense in all situations.<BR/><BR/>For any practice, there will be corner cases and how you handle them will depend on your exact circumstances. As with traditional development, people have to make judgment calls. Those twelve bugs might all be trivial and while reported and good to know about, nobody cares that they have to wait until the next release to get it fixed. On the other hand, one of them might be quite serious and require an immediate patch.<BR/><BR/>Here's a question for you. What is the connection between the frequency of release and how often you upgrade? You seem to imply that it is 1-1. Why? Isn't it more likely that you will upgrade when you have a good reason to do so and that might still only be once a year?<BR/><BR/>See also my latest post, <A HREF="http://damonpoole.blogspot.com/2008/01/tuning-frequency-of-your-releases.html" REL="nofollow">Tuning the Frequency of Your Releases</A> which is my most comprehensive post on release frequency to date.Damon Poolehttp://www.blogger.com/profile/16561311551267979837noreply@blogger.com