One of the reasons Justin may think we have trouble getting enough votes is because of another interesting dynamic in Flex. When someone votes -1 on an RC because they found what they think is an important bug, folks tend to stop testing and voting. I’ve actually tried not voting -1 and simply asking for another RC in the DISCUSS thread, but I’m not sure that helped either. The finding of an important issue just stops things in their tracks.
What happens next is that voters wait for an RC with those issues fixed. In just about every instance, as soon as a good quality RC is made available we get enough votes. Because Justin often resists making another RC, it probably appears to him that we have trouble getting enough votes. I believe the only time it didn’t happen was this last release when Justin didn’t want to carry over votes for the NOTICE and xml file change. Bertrand, do you know if other projects have this kind of problem and how they deal with it? Also, I am under the impression that a +1 vote means you have actually examined the package, which is why we added the notion of carry-overs. A carry-over means that you didn’t examine the package but trust by inference that nothing changed that would change your +1 vote from a previous RC. Is there such a distinction or can we +1 by inference? Thanks, -Alex On 12/5/14, 4:49 AM, "Tom Chiverton" <t...@extravision.com> wrote: >That's true for me. If it's got enough votes to pass, by people I trust, >and I'm really busy, then I wont test it myself, or it I do it wont be >formally enough to be worth a +1 > >Tom > >On 05/12/14 12:14, Erik de Bruin wrote: >> I think what we've seen is that all VOTEs get just enough votes to >> pass because once enough passing votes are in, people choose to spend >> the little time they have available for the projects on something >> else. >
