Basho closed about leveldb

[russelldb]

@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.

[matthewvon]

@haneefmubarak Nope. No write access. I am only a guest in this repository now. My apologies. "devel" is shippable.

[randysecrist]

A pleasure working with you sir.

[lemenkov]

Too sad to hear that. Anyway let's hope Riak survives all that mess.

[dyu]

"At that time, I will restore hot backup code to the open source base

So I guess it was intentionally removed from the open source version?
Anyway, hot backup has always been available in hyperleveldb

[haneefmubarak]

@matthewvon could you tag the existing code as a release version? Thanks!

[haneefmubarak]

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!

[russelldb]

@haneefmubarak can you explain why?

[haneefmubarak]

@russelldb: so as @matthewvon mentioned, the code on branch develop is shippable as is.

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 xxxyyyzzz or worse yet HEAD). Seeing as there have been significant (important and useful) changes since the last release and it does not appear that there will be more of such changes in the immediate future, making a release is the right thing to do.

[russelldb]

@haneefmubarak we are about to make a release of riak though, and another coming in later summer/autumn (probably)

[haneefmubarak]

@russelldb awesome!