What caused it to have such a short deadline? Did we do something to cause it to be so short or is that the default and we just didn't know to override it somehow?
-- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: 631-835-4771 On Tue, Jan 19, 2016 at 8:36 PM, Roman Shaposhnik <[email protected]> wrote: > On Tue, Jan 19, 2016 at 8:18 PM, Niall Pemberton > <[email protected]> wrote: > > On Tue, Jan 19, 2016 at 9:53 PM, Nitin Lamba <[email protected]> wrote: > > > >> This is the first release for Apache Geode, version 1.0.0-incubating.M1. > >> Thanks to all the community members to drive towards this first > milestone! > >> > >> It fixes the following issues: > >> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420&version=12334248 > >> > >> *** Please download, test and vote by Wednesday, January 20th, 1700 hrs > US > >> Pacific. > >> > > > > Votes typically run for at least 3 days at the ASF to allow people time > to > > review/vote. Its not a fixed rule, but I think there needs to be a good > > reason for reducing the time. I've had to stay up late in order to review > > this before your deadline since I dont get time to do this in my $job. > Just > > my 2cents, but I think it would be more inclusive to stick to the normal > 3 > > days. > > Super strong +1 to the above! Personally, there's not way I can review > under this deadline (and I suspect neither could any of the mentors). > > Thanks, > Roman. > > P.S. Although, arguably one way for podling to learn this is the hard way. > If you don't get any binding votes under such a tight deadline you kind of > get the idea of why votes like this in ASF run for at least 72 hours. >
