Add deprecation notice to website #251
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cosmojg
approved these changes
May 15, 2023
|
PR could also link to a fork of this project https://github.com/duckdblabs/db-benchmark |
|
Hello @jangorecki, thanks for this project! I agree, would be great to add a link to the maintained fork. |
|
Would be good to also:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now the website states that benchmarks are continuously updated. This is no longer true as of July 2021.
It would be good to add a deprecation notice to show that the website has no longer been updated. This doesn't take away from the great work this benchmark has been. It's still useful. But it's good to be precise and not misleading.
It is not good for H2O's reputation to offer a website that is not accurate, promising continuous updates when these are not happening. This could be understood as H2O not being a stable provider that cares about keeping software properly maintained. Maybe @arnocandel @mattdowle one of you can have a look? Thanks!
Partially resolves #248