I've adopted a strategy (on flexvite.com) where I test and push each change immediately, but periodically roll-up and announce a list of changes since the last roll-up.<p>I'm still calling these roll-up summaries 'releases' on the web site since people are familiar with that concept.  I've received some positive feedback about using this approach.  People like the immediacy of how quickly their feedback is addressed, but they also like being able to thumb through a summary of "What's new" since they last looked.<p>Here are some examples of those summary pages (they look just like release changelogs):
1. <a href="http://blog.flexvite.com/2009/12/17/flexvite-splat-release/" rel="nofollow">http://blog.flexvite.com/2009/12/17/flexvite-splat-release/</a>
2. <a href="http://blog.flexvite.com/2009/11/11/pow-10-new-flexvite-beta-improvements/" rel="nofollow">http://blog.flexvite.com/2009/11/11/pow-10-new-flexvite-beta...</a>
3. <a href="http://blog.flexvite.com/2009/10/12/14-new-flexvite-beta-improvements/" rel="nofollow">http://blog.flexvite.com/2009/10/12/14-new-flexvite-beta-imp...</a><p>The hardest thing for me is deciding where to draw the line and do an announcement of changes that have been released recently.   I've  considered announcing individual changes one-by-one as they happen on appropriate mediums (i.e.-twitter), but it seems like it would be a little spammy.