My read of the discussion is source artifacts are your release and should not contain binaries. You can also provide signed binary "convenience artifacts", and they could possibly contain source.
What we do for HBase is a source tarball and then one convenience binary tarball without source for each of Hadoop 1 and Hadoop 2. On Monday, February 24, 2014, James Taylor <[email protected]> wrote: > I'll spin this up today. Two questions: > - Should the binary "convenience artifact" tar *not* contain source or > contain source? > - Do we need to vote on the next RC, as I've included a new bug fix in > there? I propose we just start a new vote on the general list, but I'm fine > either way. > > Thanks, > James > > > On Mon, Feb 24, 2014 at 10:36 AM, Andrew Purtell > <[email protected]<javascript:;> > >wrote: > > > There was more on general@ about this today. > > > > Current consensus seems to be that a source tarball which does not > contain > > binaries is required, this becomes the release. Additional pre-built > > binaries are optional "convenience artifacts" > > > > > > > > On Sat, Feb 22, 2014 at 2:51 AM, Steven Noels > > <[email protected]<javascript:;>> > wrote: > > > > > Guys, > > > > > > the way I read the comment from Sebb on general@inc it's probably > > > easiest if there's a separate src tarball available as a release > > > artefact. > > > > > > Steven. > > > > > > > > > > > -- > > Best regards, > > > > - Andy > > > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > > (via Tom White) > > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
