-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Documentation]: absent documentation about v4 #2008
Comments
Looks like you are still using the master branch. Checkout the new main branch (master has been deprecated, main is now the default). You'll find all the relevant information in the README. We also post releases on Github with some additional information: https://github.com/dgraph-io/badger/releases Regarding Badger v4.0.0, the tag still exists in the repository, so you can audit it / The main reason we moved to v4 is because we wanted to move away from CalVer.
We are actively developing Badger but a v5 release is not planned in the near term. |
@joshua-goldstein I don't see what you mean, I'm on the default branch which is
|
Hmm I see one source of confusion: the link to the README still uses master in the url. I opened #2011 to fix that. From the changelog (and release notes):
I agree the README is out of date. It will have to be cleaned up. In the meantime refer to the changelog and release notes for information about v4 and future releases. |
There are no proper release notes for v4.0.0
It's not on the readme:
it's not in the changelog
https://github.com/dgraph-io/badger/blob/master/CHANGELOG.md
it's not in the "choosing a version"
https://github.com/dgraph-io/badger#choosing-a-version
v4.0.0 is missing
even assuming github's release tab is now the source of truth, v4.0.0 is missing from https://github.com/dgraph-io/badger/releases/
It is unclear if v4.0.1 shows difference between v4.0.1 or prior v3 version.
I understand v4.0.0 is redacted but I think the github release should still exists and have a big bold "DO NOT USE THIS RELEASE" statement to capture history.
I wasn't able to find a rational about v4
Was the on disk format changed ?
Why are the reasons this forked out of v3 ?
What are the future implications for supported versions ?
Will a v5 happen soon and require me to migrate all of my data if I want to update ?
Most of theses questions could be solved by looking at the code, but I don't know badger's codebase and I'm not sure I would pickup all the subtleties correctly.
After some searching I was able to find 31b7588:
But the conflicting information in the readme is still very meh.
The text was updated successfully, but these errors were encountered: