Re: Signing releases with pwendell or release manager's key?

Sparks release pipeline is automated and part of that automation includes securely injecting this key for the purpose of signing. I asked the ASF to provide a service account key several years ago but they suggested that we use a key attributed to an individual even if the process is automated. I

Re: Signing releases with pwendell or release manager's key?

Would any of Patrick/Josh/Shane (or other PMC folks with understanding/opinions on this setup) care to comment? If this is a blocking issue I can cancel the current release vote thread while we discuss this some more. On Fri, Sep 15, 2017 at 5:18 PM Holden Karau wrote: >

Re: [VOTE] Spark 2.1.2 (RC1)

Yes, It doesn’t work in 2.1.0 and 2.1.1, I create a PR for this: https://github.com/apache/spark/pull/19259 . > 在 2017年9月17日，16:14，Sean Owen 写道： > > So, didn't work in 2.1.0 or 2.1.1? If it's not a regression and not critical,

Re: [VOTE] Spark 2.1.2 (RC1)

So, didn't work in 2.1.0 or 2.1.1? If it's not a regression and not critical, it shouldn't block a release. It seems like this can only affect Docker and/or Oracle JDBC? Well, if we need to roll another release anyway, seems OK. On Sun, Sep 17, 2017 at 6:06 AM Xiao Li