Honestly 72 hours is a little too little, especially if a weekend is involved, but 30 days feels way too much, especially if critical bug fixes or security issues are in play. (Hopefully rare but it does happen.) Sometimes we have more than one release in 30 days. Maybe 7 days, with some sort of emergency rip cord for critical issues?
-1 on 30 days On Fri, May 12, 2023 at 5:33 AM Tamás Cservenák <csta...@apache.org> wrote: > > Howdy, > > I'd like to propose a change to the ASF Maven voting process (in line with > ASF guidelines): > CHANGE the current "vote open for at least 72h" window to "vote open for at > least 30 days, or more". > > Reasoning: > According to paperwork (ASF stats) we have more than 90 voters available > (PMCs + committers). > Still, multiple release votes recently were able to pass the "doorstep" > only by "hunting down" voters and pulling their sleeves (apologies and > thanks to them). This makes it clear that ONLY 72h is totally > anti-community and disrespectful. Nobody's sleeve should be pulled. That's > disrespectful for sleeves as well (except if you wear a T-shirt). We must > serve our project community in the best manner, and let our voters be able > to cast well thought votes in a timely manner, hence increasing the > irrationally short window of opportunity for casting votes IS A MUST. And > leave the sleeves alone. > > Sorry, but the vote is open for at least 72 hours ONLY. > > [ ] +1 > [ ] +0 > [ ] -1 -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
