On Fri, May 29, 2009 at 3:28 PM, Greg Brown <[email protected]> wrote: > I know we need to build a new release candidate to address these issues. I > was just trying to prevent multiple internal iterations before presenting the > final PMC vote.
You can't. You'll have to roll the release again, and again, and again, and again, and again until there are no more issues. You can wait until most issues have been discovered, roll the release again to optimize the process a bit. A vote is on the actual tag/distribution that is being sent out. Part of what is going to change in the future is that a +1 vote also means having the voter *sign* the release as well, making the web of trust for the release more secure. Therefore we need to vote on the actual stuff that gets released, not a promise of what is going to be released. Martijn
