-
Notifications
You must be signed in to change notification settings - Fork 534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Riak KV 3.0 documentation? #1067
Comments
No, as we've been putting out new releases https://github.com/basho/basho_docs has not been kept up to date. I know at one stage @Bob-The-Marauder (whose company hosts docs.riak.com) had an alpha version of docs which added release notes etc for 2.2.6. I don't know if there are any plans from Nic to release this and update it further, so we at least recognise the existence of these later releases. Something should be done, but I have been as guilty as anyone of neglecting this responsibility. |
Thanks for the shout @martinsumner . Actually we are working on KV 2.9.x and KV 3.0.x docs as we speak. As with many things like this, customer focussed work takes priority but we are making progress, especially now we have three engineers working on it when not on customer support. We've noticed that some of the pre-existing stuff was actually broken and we've had to re-write things such as the Sets examples for Java as the examples given simply just didn't work. The current 2.2.6 docs are at https://www.tiot.jp/riak-docs/riak/kv/2.2.6/ and newer releases will be added to the same site as and when they become available. |
@Bob-The-Marauder After finishing those docs, will you push them to https://github.com/basho/basho_docs or some other git repository? |
Sorry for the far overdue response. Yes, we have an ongoing pull request from August 2023 - basho/basho_docs#2533 |
Repository website is http://docs.basho.com/, which redirects to https://docs.riak.com/. But the latest documentation there is for Riak KV 2.2.3. Is the 3.0 docs not ready yet?
The text was updated successfully, but these errors were encountered: