@isuntsov-gridgain how's the Ignite version number update coming? I'd like to cut an RC this weekend.

waiting on #1205

okay #1205 has landed. RC this evening when I'm off of work.

release candidate 1 is now up: https://github.com/brianfrankcooper/YCSB/releases/tag/0.15.0-RC1

As a reminder, testing a given binding should at a minimum run through a load and a run phase. Ideally, one should go through the recommended sequence of workload steps from the "Running the workloads" section of the Core Workloads documentation.

@isuntsov-gridgain could you test the Ignite related bindings in the RC?

@adamretter or @Vogel612 could you test out the RockRB bindings in the RC?

@dbjoa could you test out the FoundationDB bindings in the RC?

@mpv1989 could you test out the updated ArangoDB bindings in the RC?

@ctubbsii or @joshelser have time to check out the updated Accumulo binding in the RC?

@busbey, I've tested the FoundationDB bindings in the RC according to your guide, but no issues are found.

@busbey tested ArangoDB bindings in tag 0.15.0-RC1. No issues.

@busbey The RocksDB bindings in the RC appear to be good.

I tried out using the new minfieldlength and minscanlength with workload e and it checks out fine.

tried testing against an Accumulo 1.9.2 cluster with kerberos and ran into #1211. not a new thing AFAICT. I'll get a cluster without kerberos and try that.

verified the accumulo1.7 and accumulo1.8 bindings with both Apache Accumulo 1.9.2 and Cloudera's Accumulo packaging 1.7.2-cdh5.5.0 (on clusters that didn't use Kerberos for Accumulo client access).

I'll go ahead and close out the release in the next few days. if someone has a chance to test out the ignite stuff before then it'd be great.

@busbey
I've checked Apache Ignite 2.6.0. Looks good for me.
Also I made a PR: #1213.
It contains changes of README.md for Apache Ignite.

@busbey I've created the same pr (#1214) to staging-0.15.0.
I see that master doesn't have changes from my previous PR #1189

master has the changes from PR #1189 here: 7e19b75

are the README updates needed for this release or would they be fine waiting for the release next month?

@mpv1989 any specific version number for ArangoDB testing?

@dbjoa any specific version number for FoundationDB testing?

@adamretter I presume the testing for RocksDB was 5.11.3 since it's embedded?

It would be nice to include updated README to this release.

Okay, that's fine by me so long as we can get the PR merged in the next day or two.

Here's a DRAFT for release notes. I can update them to include specifically tested versions in a way that matches what's currently listed for Accumulo and Ignite.

https://gist.github.com/busbey/77bf0f4bbbf122f73b5dd0844210991e

what do folks think?

@busbey I tested arangodb binding against ArangoDB 3.3 and nightly build (upcoming 3.4)

release note draft updated with ArangoDB testing info. thanks!

@busbey I tested the binding with FoundationDB 5.2.5.

the readme update for ignite has been merged and brought back to the 0.15.0-staging branch. I don't think we need a new RC for the docs change (it'll get picked up when I make the release artifacts), let me know if you disagree @isuntsov-gridgain.

I updated the release notes with the foundationdb version. thanks!

release tag is ready to go and I have all the artifacts staged.

anyone have a chance to review the release notes yet?

Reviewed the release notes. Look good to me. You might want to add a line indicating that JDK 9, 10 and 11 have been tested and are now supported for many bindings.

thanks for the review!

I don't think we're ready to call out later than jdk8 as supported yet. The Travis-CI runs are an enabling step, but we don't have good documentation yet on what bindings downstream should expect to have work (as an example of our short comings on the topic).

release is up: https://github.com/brianfrankcooper/YCSB/releases/tag/0.15.0

@busbey :-) yay. Thanks:-)

Can someone take a look at #1216 so we can close out the release?

If it's just the change of version number in the readme, then that looks good to me