Agree. And on a side note, to make it easier for the community, the email should include a date for the "deadline" of voting, instead of saying "it will be open for at least 72 hours". WDYT?
Thanks, Ken On Mon, Mar 17, 2025 at 2:59 PM Jamie G. <jamie.goody...@gmail.com> wrote: > I tend to agree here. > > Full builds with all unit tests on AMQ can take 4 to 5 hours , if one is > testing many jvm vendors & platforms it can take a few days just to get > coverage. Weekend releases can make it challenging to complete them all. > > On Mon, Mar 17, 2025 at 19:23 Christopher Shannon < > christopher.l.shan...@gmail.com> wrote: > > > The Apache guideline for voting is that votes should run for at least > > 72 hours [1] but nothing prevents a vote from going longer. It also > > doesn't specify anything about votes on weekends or not but just > > generally 72 hours. > > > > Because there isn't a maximum time for votes, (I've seen votes go > > weeks on some projects), I think it would be a good idea if we adopted > > a policy where we don't count weekend days or major holidays etc to > > allow for everyone 3 business days to be able to have a chance to > > review a release and vote. > > > > This doesn't have to be something super strict, we don't need to go > > crazy counting holidays as they can vary by country and region, but > > major holidays like New Years make sense. Urgent releases can also > > always go out quicker if needed, I just think it would be a nice goal > > for most releases though. > > > > Thoughts? > > > > [1] https://www.apache.org/foundation/voting.html > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org > > For additional commands, e-mail: dev-h...@activemq.apache.org > > For further information, visit: https://activemq.apache.org/contact > > > > > > >
