+1 for 0.12.2.

We would rather have those fixes now than wait till 0.13.

Prashant


On Wed, Jun 20, 2018 at 11:55 PM Gian Merlino <g...@apache.org> wrote:

> I think we're hoping that the next major (0.13) will also be our first
> Apache release. If it ends up taking too long we might want to rethink that
> but hopefully it won't (see the recently started thread about the next
> step, migrating the Github repos).
>
> On Wed, Jun 20, 2018 at 10:42 PM Roman Leventov <leventov...@gmail.com>
> wrote:
>
> > Why won't release 13.0 instead (as non-Apache)?
> >
> > On Thu, 21 Jun 2018, 08:18 Gian Merlino, <g...@apache.org> wrote:
> >
> > > +1
> > >
> > > I would suggest adding these two as well.
> > >
> > > https://github.com/druid-io/druid/pull/5878 - Fix inefficient
> available
> > > segment cache population in SQLMetadataSegmentManager.
> > > https://github.com/druid-io/druid/pull/5873 - HdfsDataSegmentPusher:
> > Close
> > > tmpIndexFile before copying it.
> > >
> > > On Tue, Jun 12, 2018 at 11:34 AM Prashant Deva <
> prashant.d...@gmail.com>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > On Fri, Jun 8, 2018 at 3:37 PM Jihoon Son <jihoon...@apache.org>
> > wrote:
> > > >
> > > > > Hi guys,
> > > > >
> > > > > we have a couple of bug fix PRs available and some of them fix
> > > regression
> > > > > bugs.
> > > > >
> > > > > Here is the list of currently available bug fix PRs which are not
> > > > included
> > > > > in 0.12.1.
> > > > >
> > > > > Regression bug fixes
> > > > > - https://github.com/druid-io/druid/pull/5858
> > > > > - https://github.com/druid-io/druid/pull/5805
> > > > > - https://github.com/druid-io/druid/pull/5807
> > > > >
> > > > > Non-regression bug fixes
> > > > > - https://github.com/druid-io/druid/pull/5850
> > > > > - https://github.com/druid-io/druid/pull/5815
> > > > > - https://github.com/druid-io/druid/pull/5856
> > > > >
> > > > > I think it's worth to make another release for users.
> > > > >
> > > > > Welcome any idea.
> > > > >
> > > > > Jihoon
> > > > >
> > > > --
> > > > Prashant
> > > >
> > >
> >
>

Reply via email to