Technically, this vote doesn't expire until 1930EDT, but I don't plan on
voting on this one, and it doesn't look like it'll pass as-is. I'll create
an RC2 on Monday, if this vote fails.
On Fri, Sep 23, 2016 at 5:35 PM Keith Turner wrote:
> On Wed, Sep 21, 2016 at 11:13 PM, Josh Elser wrote:
> >
On Wed, Sep 21, 2016 at 11:13 PM, Josh Elser wrote:
> +1 (binding)
>
> First off, interesting use of the fetch.sh script to circumvent any extra
> licensing in Fluo. I feel like this kind of goes against the intent of the
> LICENSE and NOTICE files (they're meant to be there so that users know you
-1
The default config in the tarball has SNAPSHOT for the Fluo version in
the config for Accumulo iterators. This causes things to break out of
the box.
The signature on the tarball looked good. I was able to build Fluo
Recipes and Webindex against the staging repo. I was also able to run
the
FWIW, I will stage in SVN before IPMC vote. I've also been thinking of ways
to automate that part for the future. :)
On Wed, Sep 21, 2016, 23:13 Josh Elser wrote:
> +1 (binding)
>
> First off, interesting use of the fetch.sh script to circumvent any
> extra licensing in Fluo. I feel like this ki
+1 (binding)
First off, interesting use of the fetch.sh script to circumvent any
extra licensing in Fluo. I feel like this kind of goes against the
intent of the LICENSE and NOTICE files (they're meant to be there so
that users know your product depends on and those licenses), but I can't
cit
Fluo Developers,
Please consider the following candidate for Fluo 1.0.0-incubating.
Git Commit:
b07fbf8b755e8f555d06fe2d57db2868f9b20c1c
Branch:
1.0.0-incubating-rc1
If this vote passes, a gpg-signed tag will be created using:
git tag -f -m 'Apache Fluo 1.0.0-incubating' -s
rel/fluo-
