Hi Andrew, Thank you for starting discussion.
> We're thinking about a "fix-and-iterate" approach, just to get the currently > ongoing releases out the door. It's a good choice and I agree with you basically. My impression, however, is that we should stop *binary distribution* and we should only provide *source distribution* for the release until the problem will be fixed after checking your patch on HADOOP-12893. It's because our binary distribution includes LGPL files which should not be included as Apache products[1]. I know that it introduces us the inconvenience, but it looks safer choice to me for protecting our Apache Hadoop project. As Xiao and Sean mentioned, we should introduce maven-remote-resources-plugin as soon as possible. After doing this, we can resume binary distribution. Thoughts? [1] LICENSES MAY NOT BE INCLUDED WITHIN APACHE PRODUCTS, http://www.apache.org/legal/resolved.html [2] http://maven.apache.org/plugins/maven-remote-resources-plugin/ Bests, - Tsuyoshi On Mon, May 16, 2016 at 10:43 AM, 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 --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
