Presuming your &quot;productivity&quot; stays the same, you would either have 16 releases of size &quot;1&quot; after two days, or 1 release of size &quot;16&quot;. Either way, the size of the code to examine would be the same, right?
You would still have the benefit of getting the new features faster to the user, so I would say quick releases are still beneficial.<p>In your situation, I would look for ways to detect the issues earlier. Ideally, you know about it before the user does (which is easier said than done, I know). Added benefit of this: quicker feedback will help you pinpoint the problematic release ;-)