Hey All,
Would like to start the vote today or tomorrow. I still would like to get a
few straggling patches in if possible.

I'm hoping the following issues get closed out today:

DRILL-971 (CSV Headers)
DRILL-3963 (Sequence File)
DRILL-1410 (Parquet fork)
DRILL-3793 (RecordIterator)
DRILL-3796 (Fix wrong result in merge join)

I also saw an apparent regression in MSSQL plugin functionality so I'll be
taking a quick look at that.

I know that Jim was also looking at the HTTPD format plugin (DRILL-3423) so
I'm holding out hope that he has an updated (and mergeable patch) today.

Any last things we'd like to get in before we generate a release candidate?

thanks,
Jacques


--
Jacques Nadeau
CTO and Co-Founder, Dremio

On Wed, Oct 28, 2015 at 8:05 PM, Jacques Nadeau <[email protected]> wrote:

> Great, thanks for you flexibility!
>
> I think this will be very helpful to the people struggling with some of
> the jdbc issues right now.
>
> One other nice thing is that this will get Julien's changes out to users.
> It wasn't mentioned in the jira but his changes should make embedded mode
> startup 2-3 seconds faster.
> On Oct 28, 2015 5:25 PM, "Parth Chandra" <[email protected]> wrote:
>
>> No one else seems to have an opinion :)
>>
>> Let's go with the monthly cycle with the vote going out at the beginning
>> of
>> the month starting with the 1.3 release.
>>
>> Let's also make sure we stick to this cycle for all future releases.
>>
>> Parth
>>
>>
>>
>>
>>
>> On Mon, Oct 26, 2015 at 7:06 PM, Jacques Nadeau <[email protected]>
>> wrote:
>>
>> > Hey Parth,
>> >
>> > Unfortunately, I didn't see the notes earlier or I could have provided
>> > feedback earlier. We've been talking about doing monthly time-bound
>> > releases for some time and since the last release was started at the
>> > beginning of the month, our expectation was that 1.3 would be at the
>> > beginning of November. There are a number of issues that we see people
>> > hitting that we should be able to resolve around the JDBC plugin this
>> week
>> > thus our desire to start the vote next week.
>> >
>> > How does that sound?
>> >
>> > thanks!
>> > Jacques
>> >
>> > --
>> > Jacques Nadeau
>> > CTO and Co-Founder, Dremio
>> >
>> > On Mon, Oct 26, 2015 at 6:33 PM, Parth Chandra <[email protected]>
>> > wrote:
>> >
>> > > I remember that the we settled on sending out for vote on the 12th.
>> > >
>> > > Minutes from the hangout :
>> > >
>> > >
>> >
>> https://docs.google.com/document/d/1o2GvZUtJvKzN013JdM715ZBzhseT0VyZ9WgmLMeeUUk/edit#heading=h.wlenwxcj8f7t
>> > >
>> > >
>> > > On Mon, Oct 26, 2015 at 5:49 PM, Jacques Nadeau <[email protected]>
>> > > wrote:
>> > >
>> > > > I thought we talked about the middle of each month and then you
>> > suggested
>> > > > moving to the beginning of the month as that is easier to
>> remember.  Of
>> > > > course I can't find the thread about this.
>> > > >
>> > > > My preference would be get going start-of-month time-bound releases
>> > > > starting next week unless you have a big concern. Sound okay?
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Jacques Nadeau
>> > > > CTO and Co-Founder, Dremio
>> > > >
>> > > > On Mon, Oct 26, 2015 at 2:16 PM, Parth Chandra <[email protected]>
>> > > wrote:
>> > > >
>> > > > > No problem with moving to the monthly cycle, but I thought that we
>> > were
>> > > > > going to target the 12th of each month as the vote date.
>> > > > >
>> > > > > On Mon, Oct 26, 2015 at 11:40 AM, Jacques Nadeau <
>> [email protected]
>> > >
>> > > > > wrote:
>> > > > >
>> > > > > > Hey Guys,
>> > > > > >
>> > > > > > We talked about moving to a start of month release cycle and
>> we're
>> > > > > > approaching a start of month.
>> > > > > >
>> > > > > > I'd like to volunteer for the next release and target next week
>> as
>> > a
>> > > > > target
>> > > > > > voting period. Let's see what we can get merged this week and
>> then
>> > > use
>> > > > > the
>> > > > > > Sat - Tues for stabilization. (Target vote on Tuesday
>> afternoon.)
>> > > > > >
>> > > > > > Let me know your thoughts.
>> > > > > >
>> > > > > > Jacques
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>

Reply via email to