Appreciate the feedback - understand the vote is still ongoing but wanted to acknowledge the comments.
Will investigate how to have the build process for the convenience binaries not add the auto-generated dependencies file and for it to use our license rather than the stock one. Will also look into options for making the NOTICE file appear more customary with other projects. Regarding the license/notice being different for binary vs. source releases if anyone has pointers to examples of this that would be helpful. As it is right now while I do agree it is complex it does also appear to consistent with the ASF guidance found regarding license/notice handling. If there is an easier and less complex way we'd love to do that. Thanks! Joe On Wed, Jan 28, 2015 at 6:40 PM, Benson Margulies <bimargul...@gmail.com> wrote: > On Wed, Jan 28, 2015 at 6:05 PM, jan i <j...@apache.org> wrote: > > +1 (binding) > > > > I am a bit confused about the mangling of license/notice files in respect > > of the source/binary releases. > > > > Can I please ask you to make a clear distinction between source and > binary > > (which is not official ASF release) in the next release. > > > > On side note, I am still not quite comfortable having binary releases, > we > > (the incubator in general) need a discussion on how we look at jar files, > > they are not really object files (as from C/C++) but they are still > binary. > > I acknowledge and DO NOT dispute the fact that java projects needs this. > > Jan, I'm not sure precisely what you are uncomfortable about, but I > note that > http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven > is official. The Apache Maven Project, just to cite an example, puts > up several releases a month like this. We run the release plugin, it > produces the 'official source release' bundle which is cited in the > vote, and it also stages the binaries. All of this is staged in > repository.apache.org. Maybe the correct response is, 'You don't look > at binary files. The only thing up for a vote is the official source > release bundle referenced specifically in the vote email. Pay No > Attention To The Convenience Items Behind the Curtain.' > > If you are discomfortable with this, I think it would be helpful if > you would raise this on comdev or some other venue that applies to the > Foundation as a whole, so as not to end up accidently seeming to hold > podlings to standards different than the project communities. > > regards, > benson > > > > > > > > > rgds > > jan I. > > > > > > > > On 28 January 2015 at 23:42, Billie Rinaldi <bil...@apache.org> wrote: > > > >> The source artifacts look good. The nar and war files deployed in the > >> orgapachenifi-1022 repository seem to have default LICENSE files that > don't > >> have license info for their bundled dependencies, but they do all have > >> DEPENDENCIES files listing this information. I haven't worked with > these > >> dependencies files before. Are they sufficient for communicating > license > >> information? > >> > >> On Mon, Jan 26, 2015 at 7:33 PM, Joe Witt <joe.w...@gmail.com> wrote: > >> > Hello > >> > > >> > The Apache NiFi (incubating) team is pleased to be calling this vote > for > >> > the source release of Apache > >> > NiFi 0.0.1-incubating. > >> > > >> > With six binding (in the ppmc sense) +1 votes and no dissenting votes > the > >> > PPMC has approved the vote for the release in this thread: > >> > > >> > http://s.apache.org/nifi-rc3 > >> > > >> > We now ask the IPMC to vote for this release. > >> > > >> > Since this is our first release as part of the Apache Incubator it > will > >> be > >> > slightly unique because we need to release two components. > >> > > >> > The first component is the 'nifi-nar-maven-plugin' which allows us to > >> build > >> > 'NiFi Archives' which is part of our classloader isolation model. The > >> > second is simply 'nifi' which is the full build and application that > is > >> > 'Apache NiFi (incubating)'. > >> > > >> > After this first release we expect to be releasing the > >> > 'nifi-nar-maven-plugin' very rarely. > >> > > >> > So we'll break the information sections of this vote into two parts > where > >> > one is for 'nifi-nar-maven-plugin' and the other 'nifi'. > >> > > >> > For the 'nifi-nar-maven-plugin' > >> > -------------------------- > >> > The source zip, including signatures, digests, etc. can be found at: > >> > https://repository.apache.org/content/repositories/orgapachenifi-1021 > >> > > >> > The specific repository path in that staging repo is: > >> > > >> > > >> > >> > orgapachenifi-1021/content/org/apache/nifi/nifi-nar-maven-plugin/1.0.0-incubating/ > >> > > >> > The sources.zip is called > >> > 'nifi-nar-maven-plugin-1.0.0-incubating-source-release.zip' > >> > > >> > The Git tag is nifi-nar-maven-plugin-1.0.0-incubating-RC3 > >> > > >> > The Git commit ID is 6e69d99444e22772df300cd777096dc21a7c8e35 > >> > > >> > > >> > > >> > >> > https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;a=commit;h=6e69d99444e22772df300cd777096dc21a7c8e35 > >> > > >> > Checksums of nar-maven-plugin-1.0.0-incubating-source-release.zip: > >> > MD5: 2681be25c32a45df07fbac59f768c5d2 > >> > SHA1: 1e6057e07c32a7a0208afdc36e7ce725bd9935e4 > >> > > >> > 7 issues were closed/resolved for this release: > >> > > >> > > >> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12329307 > >> > > >> > ++++ > >> > Note once you have completed the verification of the > >> > 'nifi-nar-maven-plugin' you will have > >> > 'nifi-nar-maven-plugin:1.0.0-incubating' in your local repo and thus > you > >> > can move on to the 'nifi' build below which depends on it. > >> > ++++ > >> > > >> > For 'nifi' > >> > ------------- > >> > The source zip, including signatures, digests, etc. can be found at: > >> > https://repository.apache.org/content/repositories/orgapachenifi-1022 > >> > > >> > The specific repository path in that staging repo is: > >> > orgapachenifi-1022/org/apache/nifi/nifi/0.0.1-incubating/ > >> > > >> > The sources.zip is called 'nifi-0.0.1-incubating-source-release.zip' > >> > > >> > The Git tag is 'nifi-0.0.1-incubating-RC3' > >> > > >> > The Git commit ID is 3a7625920866deaab1f3973fc4db0847d054a9b5 > >> > > >> > > >> > > >> > >> > https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;a=commit;h=3a7625920866deaab1f3973fc4db0847d054a9b5 > >> > > >> > Checksums of nifi-0.0.1-incubating-source-release.zip: > >> > MD5: f421bb67a775b9ef7e29a34c08c538c1 > >> > SHA1: a04a3914d9e5a4455c1b503785a7772ab772816c > >> > > >> > 114 issues were closed/resolved for this release: > >> > > >> > > >> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12329078 > >> > > >> > The following information applies to both the 'nifi-nar-maven-plugin' > and > >> > 'nifi': > >> > > >> > > >> > Release artifacts are signed with the following key: > >> > https://people.apache.org/keys/committer/joewitt.asc > >> > > >> > KEYS file available here: > >> > https://dist.apache.org/repos/dist/release/incubator/nifi/KEYS > >> > > >> > This vote will follow 'http://www.apache.org/foundation/voting.html' > >> > 'Votes > >> > on Package Releases' guidelines. > >> > > >> > The vote will be open for 72 hours. > >> > Please download the release candidate and evaluate the necessary items > >> > including checking hashes, signatures, build from source, and test. > Then > >> > please vote: > >> > > >> > [ ] +1 Release this package as Apache NiFi 0.0.1-incubating > >> > [ ] +0 no opinion > >> > [ ] -1 Do not release this package because because... > >> > > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
