Re: [VOTE] Release Livy 0.6.0 based on RC1

2019-03-19 Thread Marcelo Vanzin
FYI I'm cancelling this vote in favor of rc2. On Mon, Mar 18, 2019 at 2:01 PM Marcelo Vanzin wrote: > > This vote is for releasing Livy 0.6.0 based on RC1. > > The vote will be open at least 72 hours until Thursday March 21st, 21:00 UTC > and > will pass with a minimum of 3 +1 binding votes and

Re: [VOTE] Release Livy 0.6.0 based on RC1

2019-03-18 Thread Marcelo Vanzin
I played with this a bit; found out it's generated by a maven plugin enabled during the packaging. The plugin seems to list everything; if a library is multi-licensed, it will list the library multiple times. It doesn't seem there's a way to choose which license to pick for a library, and that's

Re: [VOTE] Release Livy 0.6.0 based on RC1

2019-03-18 Thread Luciano Resende
On Mon, Mar 18, 2019 at 4:03 PM Marcelo Vanzin wrote: > > On Mon, Mar 18, 2019 at 2:23 PM Luciano Resende wrote: > > Also, there are lots of version mismatching between the included jars > > and the third-party license file > > Could you be a little more explicit about this one? I don't even see

Re: [VOTE] Release Livy 0.6.0 based on RC1

2019-03-18 Thread Marcelo Vanzin
On Mon, Mar 18, 2019 at 2:23 PM Luciano Resende wrote: > Also, there are lots of version mismatching between the included jars > and the third-party license file Could you be a little more explicit about this one? I don't even see a 3rd party license file. What exactly is the expectation here?

Re: [VOTE] Release Livy 0.6.0 based on RC1

2019-03-18 Thread Luciano Resende
-1 There has been a lot of discussion around this, but at the moment it's not acceptable to have binary jars in a source release. Also, there are lots of version mismatching between the included jars and the third-party license file Minor: Extract folder should prefix apache in the name (e.g.