These are guidelines. We make our own rules. The important part is that we make sure we are inclusive of people all around the planet.
A hotfix is a different situation, we need to get it out fast and since it is not a significant change, a quick window should be fine. > [1] ... Votes should generally be permitted to run for at least 72 hours to > provide an opportunity for all concerned persons to participate regardless of > their geographic locations. ... ‘Generally’! We shortened this for releases at some point, there is probably a vote thread back there somewhere. Note that 72 hours still applies to votes nominating new pmc/committers. Going deeper, I see a trend where we question process and rules. I find this to be a distraction from the actual work. I am of the mind that we are all trustworthy, able to constructively and openly discuss things and this formality can be a barrier to moving forwards. Maybe newer committers need clearer guidelines and I have just been around too long to be objective, that is a possibility too. Cheers, Jesse [1] https://www.apache.org/foundation/votinhttps://www.apache.org/foundation/voting.html#ReleaseVotesg.html#ReleaseVotes > On Sep 28, 2018, at 1:56 AM, julio cesar sanchez <[email protected]> > wrote: > > This is being discussed in slack and github > <https://github.com/apache/cordova-coho/issues/202>, but I think it belongs > to the mail list. > > There is a discrepancy in the duration of the votes. > > Apache states that: > Release votes SHOULD remain open for at least 72 hours. > > But in coho vote templates we have: > Voting will go on for a minimum of 48 hours. > > Also both of them say "at least" or "a minimum", but not sure if sometimes > there can be exceptions to speed things up.
