On 09/11/2014 10:20 AM, Julien Le Dem wrote:
So it boils down to publishing a signed zip or tgz of the repo?
On Thu, Sep 11, 2014 at 7:55 AM, Jake Farrell <[email protected]> wrote:
-1, Releases must contain a source release and optionally a binary release
such as the published jars, they can not just be a link to the current git
repo and staged jars.
We need to follow the release management guide for this [1], specifically
all the following points
-Jake
Thanks, Jake. I thought that the sources jar generated by maven was the
correct release artifact, but I talked with Tom and it sounds like (as
Julien says) we just need to sign a tarball of the tag.
I think we have the other items on the checklist covered, but I'll
double-check and then send out another release try.
Thanks!
rb
--
Ryan Blue
Software Engineer
Cloudera, Inc.
