Hi, I'm not against concurrent votes, but I've one concern and a few wording changes.
The concern is that this puts more work on the IPMC. At the moment, the PPMC vote filters out RCs with issues before they reach general@. With concurrent votes, the IPMC ends up reviewing RCs the PPMC would have rejected anyway, and IPMC time is the one thing we're short of. That on its own may be reason enough not to do this. If we do go ahead, both votes will still run for 72 hours, and both will be closed with a result before anything is published. The general@ vote email should still link to the dev@ vote thread so IPMC members can see it and check the tally. I'd put sequential first and say it's the default. Concurrent should be something a podling chooses, as an exception, not the expectation. Note this changes pages/policy/incubation.ad, which is Incubator policy, so it needs an IPMC vote to adopt once the wording is settled. Regarding JB's suggestion of sending one thread to both lists, I'd rather not. Replies end up on one list or the other, and the tally gets messy. Two threads running at the same time give the same result without that. Thanks, Justin
