Hi, >> 2) A slower release candidate cycle would help, IMO you'll get more >> reviews, more testing and less release candidates overall. > Fewer releases per year doesn't sound helpful to the community. release candidate != release I'm talking about how often RCs are produced in a single release cycle.
> Forcing serialized voting for our releases also doesn't sound helpful to > the community. They don't need to be serial - they need to be independent of each other if at all possible. > I thought we weren't supposed to advertise development builds on users@ A release candidate is not a development build, we should be encouraging user to test RCs as we find issues before we release + it helps with community building. We have done this in the past. > Agree, but don't' see how serializing and making the process take longer > is the way to encourage folks to step up. It's much easier for someone to take one releasing a single product than two (or four or six). Thanks, Justin
