Hi, Thanks everyone for this review, this is the TODO list before calling a vote:
1. Update 2016 to 2016-2017 in notice file. 2. Add notice and disclaimer files to incubator-rocketmq-site. 3. Remove hs_err_pid87490.log from the RC. 4. Polish the README file in RocketMQ repo. When the TODO list is resolved, we will prepare the RC and upload it to dist/dev, then call a vote. After both the PPMC vote and IPMC vote are passed, we will move the RC to dist/release/, then separately publish to maven, announce the release, update the rocketmq site. Is this process ok? Regards, yukon On Fri, Feb 3, 2017 at 9:19 AM, Justin Mclean <[email protected]> wrote: > Hi, > > > We want to do source-only release in dist-dir[1] and publish the binary > > *.jar to maven central repo, is this ok? > > The convenience binary may bundle different software and so the LICENSE > and NOTICE files continued inside may need to be different. [1] Has this > been checked? > > It’s also useful for checking the dependancies and that the convenience > binary consists only of code made from the source release. [2] > > But as the source is considered the official release and the binary just > there to help out user who don’t want to compile it there is a few way of > doing this. [3] > > Thanks, > Justin > > 1. http://www.apache.org/dev/licensing-howto.html#binary > 2. http://www.apache.org/legal/release-policy.html#compiled-packages > 3. http://www.apache.org/legal/release-policy.html#what
