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

Open
matthewvon opened this Issue Jul 13, 2017 · 11 comments

Comments

Projects
None yet
6 participants
@matthewvon
Contributor

matthewvon commented Jul 13, 2017

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

@randysecrist

This comment has been minimized.

Show comment
Hide comment
@randysecrist

randysecrist Jul 14, 2017

A pleasure working with you sir.

A pleasure working with you sir.

@lemenkov

This comment has been minimized.

Show comment
Hide comment
@lemenkov

lemenkov Jul 26, 2017

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

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

@dyu

This comment has been minimized.

Show comment
Hide comment
@dyu

dyu Aug 1, 2017

"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

dyu commented Aug 1, 2017

"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

This comment has been minimized.

Show comment
Hide comment
@haneefmubarak

haneefmubarak Mar 4, 2018

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

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

@matthewvon

This comment has been minimized.

Show comment
Hide comment
@matthewvon

matthewvon Mar 4, 2018

Contributor

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

Contributor

matthewvon commented Mar 4, 2018

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

@haneefmubarak

This comment has been minimized.

Show comment
Hide comment
@haneefmubarak

haneefmubarak Mar 4, 2018

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!

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

This comment has been minimized.

Show comment
Hide comment
@russelldb

russelldb Mar 4, 2018

Member

@haneefmubarak can you explain why?

Member

russelldb commented Mar 4, 2018

@haneefmubarak can you explain why?

@haneefmubarak

This comment has been minimized.

Show comment
Hide comment
@haneefmubarak

haneefmubarak Mar 4, 2018

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

This comment has been minimized.

Show comment
Hide comment
@russelldb

russelldb Mar 4, 2018

Member

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

Member

russelldb commented Mar 4, 2018

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

@russelldb

This comment has been minimized.

Show comment
Hide comment
@russelldb

russelldb Mar 4, 2018

Member

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

Member

russelldb commented Mar 4, 2018

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

@haneefmubarak

This comment has been minimized.

Show comment
Hide comment

@russelldb awesome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment