impala-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <>
Subject Re: Releases while incubating: looser standards
Date Fri, 22 Jul 2016 16:35:47 GMT
So long as the code grant is in place (which should have happened
before a git import) and the release had a suitable disclaimer in the
release notes, I'd be fine with that as an IPMC voter.

On Fri, Jul 22, 2016 at 11:32 AM, Jim Apple <> wrote:
> Specifically, if we are still in the midst of a copyright/licensing
> audit, but are actively working on it, would you expect that to block
> our first incubating release?
> On Fri, Jul 22, 2016 at 1:40 AM, Tom White <> wrote:
>> I agree. You don't need to wait until everything is perfect to do a
>> release, and in fact a lot of issues will get flushed out by going
>> through the release process.
>> Tom
>> On Thu, Jul 21, 2016 at 11:24 PM, Todd Lipcon <> wrote:
>>> Yes, I agree with the statement that it can be looser, but if there is stuff
>>> that is downright _wrong_ or not covered, it's likely the release will get
>>> -1s until it can be addressed. If it's something that's a bit of a grey area
>>> (eg the licensing is correct but it's not called out quite correctly in top
>>> level NOTICE files or such) then I often see a '+1, please fix the following
>>> for your next release'.
>>> On Thu, Jul 21, 2016 at 2:50 PM, Jim Apple <> wrote:
>>>> Hello Impala Mentors,
>>>> I was chatting with Sean Busbey about incubation in general, and he
>>>> mentioned that while incubating, releases are not help to as high as
>>>> standard about licensing as they are after graduation:
>>>> He mentioned that, while an incubating project is doing its license
>>>> audit and header changes, the community can still do releases, and
>>>> that this will help the community learn about the mechanics of signing
>>>> releases, votes, etc.
>>>> I wanted to check in with you, our mentors, before heading down this path.
>>>> I have CCed Sean and dev@.
>>>> Best,
>>>> Jim
>>> --
>>> Todd Lipcon
>>> Software Engineer, Cloudera


View raw message