I am a plugin developer myself and also manage a lot of installs for clients that have to be up to date.

I can relate to all the above points for one reason or another. However, there's also quite some contradiction in the statements - here and elsewhere:

@Jeffro:
It’s an annoying process to update a plugin three times a week.
That's not always "annoying" as there can be security fixes or "stupid dev errors" that causes trouble for the users --- both reasons justify prompt updates.

On the other side, there are also A LOT of users complaining if a plugin gets no update in about 3 weeks, or 3 months or so... There are also blogs - just like this one here - that constantly "warn" users to update all stuff, and also warn users to not use/download plugins that were not updated recently. That is confusing to say the least...

"Iterate quickly and release often" is an open source motto from the Linux world - it should emphasize this whole open source software culture and how all is going in general - also compared to the proprietary software world.

My real life practice is that:
I "collect" all updates on most installs I manage and make update sessions every week or every other week. That works pretty well for me and for every special difference those installs have.

For me as plugin developer I am not quite sure which route I should follow - based on the discussion. My general conviction hasn't changed: push out a "real" update (as compared to tiny fix releases...) as soon as possible. And "possible" here means WITH testing but WITHOUT rushing it. Rushing is always a source for new errors...

Thanks, Dave from Germany :)