docs: add new version of store protocol #21
Merged
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
jimstir
reviewed
Jun 5, 2024
Co-authored-by: Jimmy Debe <[email protected]>
Co-authored-by: Jimmy Debe <[email protected]>
jimstir
approved these changes
Jun 6, 2024
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.
After several rounds of review, the new Store protocol ("Store v3", although this should not be its official name) is now ready to be merged into the specs repo.
I've not updated everything in the spec, but have ensure that the links to rfc-index are working. I've also added a note to indicate this spec is earmarked to replace the current store RFC at some point.
As soon as this PR is merged, we can close the corresponding PR on the old RFC repo: vacp2p/rfc#665
It may also be a good idea to restrict visibility to that deprecated repo to avoid any confusion.