-
Notifications
You must be signed in to change notification settings - Fork 178
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
Basho closed #229
Comments
A pleasure working with you sir. |
Too sad to hear that. Anyway let's hope Riak survives all that mess. |
So I guess it was intentionally removed from the open source version? |
@matthewvon could you tag the existing code as a release version? Thanks! |
@haneefmubarak Nope. No write access. I am only a guest in this repository now. My apologies. "devel" is shippable. |
It's all good, thanks anyways @matthewvon. @russelldb wanna do like everyone here a solid and do the same (tag the current existing code as a release version)? Thanks! |
@haneefmubarak can you explain why? |
@russelldb: so as @matthewvon mentioned, the code on branch However, when using this as a dependency of a project, it is useful to be able to refer to a released version (instead of just saying grab commit |
@haneefmubarak will talk to bet365 people (who own the repo) on Monday and figure something out. Can't see a reason why we can't tag it for you, though. |
@haneefmubarak we are about to make a release of riak though, and another coming in later summer/autumn (probably) |
@russelldb awesome! |
A small note that Basho has closed down. I periodically review issues and will try to help. Feel free to ping me directly via github's messaging.
Life is busy for me, but I do plan to finish the shadow tables code and post in a cloned repository. Likely be at least September before that happens. At that time, I will restore hot backup code to the open source base. (again, contact me directly if you have urgent need for either)
Matthew
The text was updated successfully, but these errors were encountered: