Re: src-only release The primary way people consume our artifacts is the binary tarball and more importantly the Maven artifacts. Our downstreams aren't going to integrate and test without Maven artifacts. Thus (unfortunately) I don't see a src-only release being very useful.
We used to say "the src tarball is the only official release artifact, the bin tarball and jars are only provided as a convenience", but I don't think we're actually allowed to do that. On Tue, May 17, 2016 at 1:56 AM, Steve Loughran <ste...@hortonworks.com> wrote: > > > On 16 May 2016, at 02:43, Andrew Wang <andrew.w...@cloudera.com> wrote: > > > > Hi common-dev, > > > > We have a first cut of the L&N files on HADOOP-12893. Many thanks to Xiao > > Chen and Akira Ajisaka for doing the brunt of this work. However, full > ASF > > compliance will require a lot more Maven work. In the meanwhile, our > > releases are blocked. > > > > We're thinking about a "fix-and-iterate" approach, just to get the > > currently ongoing releases out the door. The intent is not to keep > kicking > > the can down the road. > > > > Since releases require a majority PMC vote, if a PMC member would -1 a > > release on these grounds, please speak up. Additional review help & > > particularly Maven wizardry is also always appreciated. > > > > Best, > > Andrew > > > > HADOOP-13154 covers a license-ish issue: a bit of S3AFilesystem is clearly > a cut and paste of the Amazon SDK. There's nothing directly wrong with > that, the SDK is ASF-licensed, we just need to call it out. In HADOOP-13130 > I've cut the code out. > > > > BTW: does anyone know why the default reply is to sender and not list > anymore? That's really annoying. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > >
