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 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 webindex on EC2 using the tarball.
On Tue, Sep 20, 2016 at 7:05 PM, Christopher <ctubb...@apache.org> wrote:
> Fluo Developers,
> Please consider the following candidate for Fluo 1.0.0-incubating.
> Git Commit:
> 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-1.0.0-incubating \
> Staging repo:
> Source (official release artifact):
> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> given artifact.)
> All artifacts were built and staged with:
> mvn release:prepare && mvn release:perform
> Signing keys are available at
> (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> Release notes (in progress) can be found at:
> Please vote one of:
> [ ] +1 - I have verified and accept...
> [ ] +0 - I have reservations, but not strong enough to vote against...
> [ ] -1 - Because..., I do not accept...
> ... these artifacts as the 1.0.0-incubating release of Apache Fluo.
> This vote will end on Fri Sep 23 23:30:00 UTC 2016
> (Fri Sep 23 19:30:00 EDT 2016 / Fri Sep 23 16:30:00 PDT 2016)
> P.S. Hint: download the whole staging repo with
> wget -erobots=off -r -l inf -np -nH \
> # note the trailing slash is needed