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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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: >>> >>> http://www.apache.org/dev/release.html#license >>> >>> 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
