-1 because would like to get a few API changes in that were just made
in before releasing 1.0.0.
I have not had a chance to review this RC. I would still like to
review this RC to look for any issues witht he release process. I
plan to look at it Mon morning, can we keep the staging repo around
On Wed, Sep 14, 2016 at 10:31 PM, Christopher <ctubb...@apache.org> wrote:
> The following is a test of my script from
> Please begin reviewing what it has produced so I can iron out the release
> process a bit, and so you can find any build-bugs prior to a release
> candidate vote with RC1.
> 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 Sun Sep 18 02:30:00 UTC 2016
> (Sat Sep 17 22:30:00 EDT 2016 / Sat Sep 17 19: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