Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Document the current procedure for versioning new queries #267

Closed
5 tasks
dnadales opened this issue Aug 1, 2023 · 0 comments · Fixed by #273
Closed
5 tasks

Document the current procedure for versioning new queries #267

dnadales opened this issue Aug 1, 2023 · 0 comments · Fixed by #273
Assignees
@dnadales @amesgen

Comments

@dnadales
Copy link
Member

dnadales commented Aug 1, 2023 •
edited
Loading

Document the current procedure for versioning new queries. We should make it easy to understand which versions need to be changed when adding a new query and how. See these lines. In particular we should document:

  • What are the CardanoNodeToClientVersions?
  • What are NodeToClientV_X?
  • What are ShelleyNodeToClientVersionY?
  • Why use a NodeToClientV_X to ShelleyNodeToClientVersionY mapping?
  • How do these versions relate?
@dnadales dnadales mentioned this issue Aug 1, 2023
Closed
2 tasks
@dnadales dnadales changed the title Document the current procedure for versioning new queries. We should make it easy to understand which versions need to be changed when adding a new query and how. See . In particular we should document Document the current procedure for versioning new queries Aug 1, 2023
@dnadales dnadales self-assigned this Aug 1, 2023
@amesgen amesgen mentioned this issue Aug 2, 2023
Merged
github-merge-queue bot pushed a commit that referenced this issue Aug 14, 2023
@amesgen
Add a document on query versioning (#273)
758e655 
Closes #267
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dnadales dnadales

@amesgen amesgen

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add a document on query versioning IntersectMBO/ouroboros-consensus
2 participants
@dnadales @amesgen