Skip to content
This repository has been archived by the owner on Oct 23, 2022. It is now read-only.

Remove the rocksdb feature #283

Merged
merged 1 commit into from
Aug 5, 2020
Merged

Remove the rocksdb feature #283

merged 1 commit into from
Aug 5, 2020

Conversation

ljedrz
Copy link
Member

@ljedrz ljedrz commented Aug 5, 2020

We no longer intend to pursue that feature; remove the related code.

Signed-off-by: ljedrz <ljedrz@gmail.com>
@ljedrz ljedrz requested a review from koivunej August 5, 2020 07:57
Copy link
Collaborator

@koivunej koivunej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is good, testing it has been quite a chore and it takes a long time to compile... Now I also realize that we haven't been testing it on CI either.

If we had been testing it, I'd be inclined to wait to allow anyone voice their concerns on it being removed, however as it's probably already rotten, if anyone wants to see rocksdb making a comeback it can always be restored (new PR, also setting up the testing).

bors r+

@bors
Copy link
Contributor

bors bot commented Aug 5, 2020

Build succeeded:

@bors bors bot merged commit 1720e16 into rs-ipfs:master Aug 5, 2020
@ljedrz ljedrz deleted the remove_rocks branch August 5, 2020 09:25
@koivunej koivunej mentioned this pull request Sep 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants