I generally read as being pure hours but I think it probably depends on voter pool size. In this case, probably 96 would be better for weekend spanning votes. On Mar 16, 2015 11:36 AM, "Julian Hyde" <[email protected]> wrote:
> What do the other members of the community think of the voting period? > What are the Apache rules or norms here? > > As you can imagine, I'm trying to strike a balance: give people a > reasonable chance to vote, but keep the process moving. Especially > important while we're in incubation, when we have another 72 hour vote (the > incubator PMC) before we can release. > > I propose the following. "The vote is open for the next N hours" in the > vote email means N elapsed hours, but the proposer of the vote should > increase N to, say, 96 hours if the vote overlaps a weekend. And we exhort > people to vote as early as possible so that we can find show-stoppers and > iterate fast. > > Julian > > > On Mon, Mar 16, 2015 at 10:15 AM, Alan Gates <[email protected]> wrote: > >> FWIW, I don't usually count weekends or holidays in my 72 hours votes. >> Too many people don't pay attention to mailing lists over the weekends. >> >> Alan. >> >> Julian Hyde <[email protected]> >> March 16, 2015 at 10:02 >> The vote for Apache Calcite 1.1 RC1 is due to close in 4 hours. We >> need two more binding +1s. Please vote. >> >> Julian >> >> >
