+1 (non-binding) I followed the release check process that Joe sent out and verified all of the hashes, signatures, and git hashes.
One question, but not a blocker for release: Should the convenience binary have a DEPENDENCIES file like the source releases? -Joey On Tue, May 12, 2015 at 10:51 AM, Mike Drob <[email protected]> wrote: > As somebody who hasn't been paying that close attention, how did we get up > to RC13? That seems really high, and I don't feel like I would have missed > that many votes. > > On Tue, May 12, 2015 at 11:28 AM, Sean Busbey <[email protected]> wrote: > >> On Tue, May 12, 2015 at 11:04 AM, Sergio Fernández <[email protected]> >> wrote: >> >> > >> > >> 2) Also related with the source distribution, but also a personal opinion, >> > I think such kind of releases with different versioning schemes make >> > developers' life much harder. For instance, this is what I needed for >> > building the releases from the source code repository: >> > >> > git clone https://git-wip-us.apache.org/repos/asf/incubator-nifi.git >> > nifi >> > cd nifi >> > git checkout 37732bddcfcb2affcba1f3b4a9e3dd5ebd7b5a30 >> > cd nifi-parent/ >> > mvn clean install >> > cd .. >> > git checkout 1fc8453b36c1a1d600a911668f10249cf1e52ea7 >> > cd nifi-nar-maven-plugin/ >> > mvn clean install >> > cd .. >> > git checkout 65a07b6b634e04f44b5b89bfaf95e0ff35c3c68c >> > cd nifi >> > mvn clean install >> > >> > which is not very convenient... >> > >> > >> >> I believe the working assumption has been that normally we won't be doing a >> nifi-parent or nifi-nar-maven-plugin release. >> >> -- >> Sean >>
