I don't view discussion as a vote blocker, and I am against anything that delays shipping. I also think adding time based on comments is treating the symptom ( uninformed + under-engaged ) when the problem was really perhaps that the discuss conversation didn't go far enough. We should definitely try to do it in the discuss thread, but a comment or a question in vote does NOT mean a -1 in my opinion.
I think one practice we could add would be to include text in the vote thread that points to the discuss thread, and invites people to re-read and comment there. @purplecabbage risingj.com On Thu, Apr 9, 2015 at 1:00 PM, Andrew Grieve <agri...@chromium.org> wrote: > That's a good point. Perhaps we should update our template to say "minium > or 48 hours, and at least 24 hours after the last non-vote comment" > > On Thu, Apr 9, 2015 at 3:58 PM, Joe Bowser <bows...@gmail.com> wrote: > > > There's nothing wrong with the practice except that a vote thread with > > comments means that we probably shouldn't proceed and should discuss it > > more. Too much discussion on vote thread means we don't have any sort > of > > consensus and should work that out first. > > > > On Thu, Apr 9, 2015, 12:52 PM Andrew Grieve <agri...@chromium.org> > wrote: > > > > > Have become very common for us. Probably because the release VOTE is > the > > > thing that actually gets people motivated to take a good look. > > > > > > Thought it'd be good for us to discuss this practice. > > > > > > My thoughts: > > > - I think it still makes sense to DISCUSS before starting a release > > > - I think it's perfectly reasonable to go through several RCs as things > > > come up during testing (RCs are easy) > > > - I think it helps to have the blog post ready before a vote (I made > this > > > change to the platforms release process this time around) > > > - I don't have any problem with VOTE threads that are full of > discussion. > > > What's the concern? > > > > > >
