On 10/12/13 3:41 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> That said, the fact is that many of the 72 hours >Do you think that have a RC votes open for 5 days rather than 3 cut down >on the number of RCs and thus the total time? IIRC, there is precedence for extending the vote past 72 hours when it covers weekends and holidays. >From my perspective, though, the number of hours the vote is open doesn't matter nearly as much as who has voted. By now, we have a good idea who on the PMC is going to even vote and which of those folks are going to take a serious look at the package. If it were me (and it isn't) before closing the vote I would make sure I've heard from those folks and ping them to see if they are going to vote or not, and extend the deadline if they want more time. Another way to cut down on RCs may be to ask on the dev list before you cut the RC. Again, you kind of know who might help you out and review the usual areas before you go packaging everything up. Those folks will likely either help out when asked or tell you they are too busy. If you had done that this time, both Erik and I would have said to wait until we get a clean mustella run since we've also seen plenty of surprises from mustella. Fortunately, the RC is still good since I decided to change the test, but otherwise asking up front would have saved you a whole round of packaging and emails. And I promise that if you do that in the future, I will take the time to read the README and RELEASE_NOTES up front since those are two areas we most often tweak between RCs. HTH, -Alex
