drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Parth Chandra <pchan...@maprtech.com>
Subject Re: Time for a 1.7 release
Date Wed, 15 Jun 2016 20:37:18 GMT
+1 on the 1.7 release

I'm reviewing the following and hope to get them in the release before
cutoff:
https://issues.apache.org/jira/browse/DRILL-2593
https://issues.apache.org/jira/browse/DRILL-4309



On Wed, Jun 15, 2016 at 1:20 PM, Jinfeng Ni <jinfengni99@gmail.com> wrote:

> I'm reviewing a follow-up PR [1] for DRILL-4573. I think we need get
> it merged in, since it's a regression in terms of query correctness
> from release 1.6.
>
> [1] https://github.com/apache/drill/pull/512
>
> On Wed, Jun 15, 2016 at 12:21 PM, Dave Oshinsky <doshinsky@commvault.com>
> wrote:
> > This is a pretty basic bug affecting decimal values, with a simple fix:
> > https://issues.apache.org/jira/browse/DRILL-4704
> >
> > It would be great if it could be reviewed.
> >
> > -----Original Message-----
> > From: Aman Sinha [mailto:amansinha@apache.org]
> > Sent: Wednesday, June 15, 2016 3:15 PM
> > To: dev
> > Subject: Time for a 1.7 release
> >
> > Hello everyone,
> >
> >   A 1.7 release is quite overdue !  I would like to get the ball
> rolling...
> >
> >   In preparation, could developers please close the pull requests that
> have already been merged into master ?  This will give me a better sense of
> what is in progress.
> >
> >   Can all the folks working on open issues let me know if there are any
> JIRAs you would like to get into the release?
> >
> >    Tentatively, I am thinking beginning of next week to get a release
> candidate.
> >
> > thanks,
> > -Aman
> >
> >
> >
> > ***************************Legal Disclaimer***************************
> > "This communication may contain confidential and privileged material for
> the
> > sole use of the intended recipient. Any unauthorized review, use or
> distribution
> > by others is strictly prohibited. If you have received the message by
> mistake,
> > please advise the sender by reply email and delete the message. Thank
> you."
> > **********************************************************************
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message