Calling the vote: +3, and no other votes. (Note, since I'm calling the vote late, I've included Billie's vote, which was received after the initial 72 hours, but since there were no -1 or +/-0 votes and I didn't get a chance to call it before she voted, this seems reasonable. IPMC, please let us know if not.)
Points raised in the vote: 1) We'll take steps to add license headers to the generated code in the build, immediately following generation, so that users will be properly informed about their re-distribution rights for these files. That change will appear in the next release. 2) It has been suggested to add "apache-" prefix to artifacts. We've thought about, and discussed this previously. I understand the reasons, but as it's not a requirement, I think we'd prefer to not do it. I'm confident we can protect the Apache Fluo brand, and promote Apache, without changing the file name. The problem is, these artifacts are generated during the automatic build process using Maven, and in order to add that prefix, it would be required to modify the Maven artifactId to redundantly add "apache" to the Maven coordinates (it already appears in the groupId), and possibly make other changes to the default build tooling. It also complicates things for downstream packaging, and is a bit unnatural for a Maven project. Since there is precedent for not doing this (including httpd, hadoop, commons, and all of the maven plugins), it doesn't seem to be required, and there are good reasons not to do it, I'm inclined to keep things as they are, but appreciate the suggestion being made. As I said, I'm confident we can protect the brand without that step. On Tue, Oct 4, 2016 at 10:51 AM Billie Rinaldi <bil...@apache.org> wrote: > +1 binding > - signatures and checksums are good > - builds from source and tests pass except GarbageCollectionIteratorIT > - source tarball matches tag > - L&N and headers look good > - DISCLAIMER is good and file names contain incubating > > On Fri, Sep 30, 2016 at 10:55 PM Christopher <ctubb...@apache.org> wrote: > > Dear IPMC, > > > > Please vote for the following release candidate of Apache Fluo > > 1.0.0-incubating. > > > > PPMC vote thread: > > > > https://lists.apache.org/thread.html/8b6ec5f17e277ed2d01e8df61eb1f1 > f42266cd30b9e114cb431c1c17@%3Cdev.fluo.apache.org%3E > > > > Staged dist artifacts: > > > > https://dist.apache.org/repos/dist/dev/incubator/fluo/fluo/ > 1.0.0-incubating-rc2/ > > > > Staged Maven repository: > > https://repository.apache.org/content/repositories/orgapachefluo-1013/ > > > > Signing KEYS: > > https://www.apache.org/dist/incubator/fluo/KEYS > > (fingerprint for this release: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D) > > > > Git repo: > > https://git-wip-us.apache.org/repos/asf/incubator-fluo > > (branch: 1.0.0-incubating-rc2, > > commit: e1dbc608c67f31e804b59abd69d0bc530ca00f77) > > > > This vote will end on Tue Oct 4 03:00:00 UTC 2016 > > (Mon Oct 3 23:00:00 EDT 2016 / Mon Oct 3 20:00:00 PDT 2016) > > > > >
