drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Volodymyr Vysotskyi <volody...@apache.org>
Subject Re: [DISCUSS] Drill 1.18.0 release
Date Sun, 14 Jun 2020 13:58:42 GMT
Hi Abhishek,

For now, I'm not sure that I'll be able to resolve DRILL-7523
<https://issues.apache.org/jira/browse/DRILL-7523> soon since there are
still a lot of unresolved issues. So please do not block the release
because of this ticket.

Kind regards,
Volodymyr Vysotskyi


On Thu, Jun 4, 2020 at 5:47 AM Charles Givre <cgivre@gmail.com> wrote:

> HI Abhishek,
> Thank you for volunteering to be release manager. Regarding the release,
> I'd like to see the PR for the Druid storage plugin committed. It's pretty
> close to being done, I'd guess another week or so. There are a few other
> PRs that Paul and I were working on which would be good to include.
>
> The recently submitted IPFS plugin would be nice to include, but we'll see
> how rapidly that progresses.  Again, thanks for your help with this.
> -- C
>
>
>
> > On May 27, 2020, at 7:27 AM, Volodymyr Vysotskyi <volodymyr@apache.org>
> wrote:
> >
> > Hi Abhishek,
> >
> > Thanks for starting this discussion and for being a volunteer for the
> > upcoming release!
> >
> > I want to include DRILL-7523
> > <https://issues.apache.org/jira/browse/DRILL-7523> into this release -
> it
> > is based on Ihor's work for updating Calcite to 1.22.
> > I'll try to complete it in a couple of weeks, but this ticket is not a
> > blocking one for the release.
> >
> > Kind regards,
> > Volodymyr Vysotskyi
> >
> >
> > On Tue, May 26, 2020 at 9:35 PM Abhishek Girish <agirish@apache.org>
> wrote:
> >
> >> Hey everyone,
> >>
> >> It's been over 5 months since the last release, so it is about time we
> >> begin to discuss the next one. I am volunteering to be the release
> manager.
> >> Vova has graciously offered me his full support with the release process
> >> and I look forward to working with you all to get this release out in
> time.
> >>
> >> We already have substantial changes in master (~130+ commits) and many
> are
> >> in the pipeline. If there are any specific issues that you feel we
> *must*
> >> include in the release, please let us know by replying to this thread.
> >> Based on that we can define the release cut off date.
> >>
> >> Regards,
> >> Abhishek
> >>
>
>

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