Following up since we haven't discussed the 1.2 release in a while. How are people feeling about trying to get a candidate out in the next week or two?
thanks, Jacques -- Jacques Nadeau CTO and Co-Founder, Dremio > ---------- Forwarded message ---------- > From: Parth Chandra <pchan...@maprtech.com> > Date: Thu, Jul 9, 2015 at 11:29 AM > Subject: Re: Timing for 1.2 release, ideas around things to include > To: dev@drill.apache.org > > > I just moved DRILL-3201 to 1.2. It's one of the candidates for inclusion > into 1.2 > > On Thu, Jul 9, 2015 at 7:04 AM, <michael.engl...@nomura.com> wrote: > > > I'm not sure what the appetite is for pushing this into 1.2 vs the > planned > > 1.3, but Drill UI Authentication would be really great for > companies/users > > that run multi-tenant Hadoop clusters with Drill. At the moment any user > > can change storage plugins and cancel running queries, even if they did > not > > submit them. This is a bit of a blocker for Drill on multi-tenant > > production clusters for now. > > > > JIRA link: > > https://issues.apache.org/jira/browse/DRILL-3201 > > > > > > > > -----Original Message----- > > From: Jacques Nadeau [mailto:jacq...@apache.org] > > Sent: 08 July 2015 17:19 > > To: dev@drill.apache.org > > Subject: Timing for 1.2 release, ideas around things to include > > > > Hey Guys, > > > > What do you think about planning the 1.2 feature cutoff around Aug 21st > > and target a release vote a week or so after that? > > > > What are different features people want to get into 1.2? > > > > Here are couple of things that I'd like to help facilitate contribution > > and/or inclusion: > > > > - Mongo improvements (including extended type fixes 2879 , test cases > 1666, > > etc) > > - httpd log parser format plugin (3423) > > - rpc enhancements (local 2941 and off-thread 3242) > > - First merge of Magnus' JDBC connector (3180) > > - New allocator (1942) > > > > Other key goals? What do people think about the proposed timing? > > > > > > This e-mail (including any attachments) is private and confidential, may > > contain proprietary or privileged information and is intended for the > named > > recipient(s) only. Unintended recipients are strictly prohibited from > > taking action on the basis of information in this e-mail and must contact > > the sender immediately, delete this e-mail (and all attachments) and > > destroy any hard copies. Nomura will not accept responsibility or > liability > > for the accuracy or completeness of, or the presence of any virus or > > disabling code in, this e-mail. If verification is sought please request > a > > hard copy. Any reference to the terms of executed transactions should be > > treated as preliminary only and subject to formal written confirmation by > > Nomura. Nomura reserves the right to retain, monitor and intercept e-mail > > communications through its networks (subject to and in accordance with > > applicable laws). No confidentiality or privilege is waived or lost by > > Nomura by any mistransmission of this e-mail. Any reference to "Nomura" > is > > a reference to any entity in the Nomura Holdings, Inc. group. Please read > > our Electronic Communications Legal Notice which forms part of this > e-mail: > > http://www.Nomura.com/email_disclaimer.htm > > > > > >
