All of the IMPALA-3200 work is now in master!

On Wed, Aug 23, 2017 at 12:21 PM, Tim Armstrong <[email protected]>
wrote:

> I was looking through open JIRAs to make sure I didn't drop the ball on
> any buffer pool changes and discovered we have 100+ open JIRAs targeted for
> 2.10: https://issues.apache.org/jira/issues/?filter=12341748
>
> It would be great to clean those up. I tried to clean up the ones that I
> know something about but most of them I'm not familiar with. It looks like
> a lot aren't being actively worked on so probably belong in the backlog -
> the target version seems to just be expressing a hope that someone else
> will fix it soon.
>
> You can check your own 2.10 JIRAs with this filter:
> https://issues.apache.org/jira/issues/?filter=12341563
>
> There are also a bunch of unassigned ones: https://issues.apache.org/
> jira/issues/?filter=12341750
>
>
>
> On Mon, Aug 14, 2017 at 11:09 AM, Bharath Vissapragada <
> [email protected]> wrote:
>
>> Agreed Tim.
>>
>> On Mon, Aug 14, 2017 at 9:13 AM, Tim Armstrong <[email protected]>
>> wrote:
>>
>> > Sounds good to me. We should coordinate to make sure that all of
>> > https://issues.apache.org/jira/browse/IMPALA-3200 (the buffer pool
>> > changes)
>> > and related fixes make it into the release.
>> >
>> > - Tim
>> >
>> > On Mon, Aug 14, 2017 at 5:52 AM, Jim Apple <[email protected]>
>> wrote:
>> >
>> > > This sounds like a good idea to me. Thank you for volunteering!
>> > >
>> > > On Mon, Aug 14, 2017 at 12:37 AM, Bharath Vissapragada
>> > > <[email protected]> wrote:
>> > > > Folks,
>> > > >
>> > > > It has been almost 2 months since we released Apache Impala
>> > (incubating)
>> > > > 2.9.0 and there have been new feature improvements and a good
>> number of
>> > > bug
>> > > > fixes checked in since then.
>> > > >
>> > > > I propose that we release 2.10.0 soon and I volunteer to be its
>> release
>> > > > manager. Please speak up and let the community know if anyone has
>> any
>> > > > objections to this.
>> > > >
>> > > > Thanks,
>> > > > Bharath
>> > >
>> >
>>
>
>

Reply via email to