What I see here is a disagreement about the meaning of the Apache brand. Some people feel that the Apache brand should always imply a particular style of project. Other people in the past have written at length that the ASF should be a big tent that accommodates many styles of project. There are already project that release frequently, including the full voting process. It's a lot of work, but they do it. So it's not true to say that 'community over code' precludes this. Some communities have chosen this. The discussion at hand is about how we could make it _easier_.
All the remarks about code quality and stability are, I think, off topic here. The reason for the release system is legal, not QA. If people think that more releases, or more automated releases, will decrease quality, then they shouldn't adopt those patterns in their communities. The question at hand should be: can we use automation to make it less labor-intensive to satisfy the legal requirements for an ASF release. Those requirements are about IP, not about QA>
