Fix branch versioning and documentation of root "statediff" branch #188

Closed
opened 2022-01-08 19:25:39 +00:00 by i-norden · 0 comments
Member

Born of #185

This transitory phase where we need to maintain and rebase two versions of the statediffing code to work with both the v0.2.x and v0.3.x versions of our database schema has highlighted some issues with our current branch/release versioning scheme and the purpose of the root "statediff" branch.

Some thing that would help:

  1. Have semantic versions, at the major/minor level, match across this repo and ipld-eth-db
  2. Maintain two root branches, one for the v2 db compatible code and one for v3 db compatible code (but we can still only have 1 default branch)
  3. Better documentation about compatibility across this repo and the others
  4. Better documentation about the purposes of the different branches in this repo
Born of #185 This transitory phase where we need to maintain and rebase two versions of the statediffing code to work with both the v0.2.x and v0.3.x versions of our database schema has highlighted some issues with our current branch/release versioning scheme and the purpose of the root "statediff" branch. Some thing that would help: 1. Have semantic versions, at the major/minor level, match across this repo and ipld-eth-db 2. Maintain two root branches, one for the v2 db compatible code and one for v3 db compatible code (but we can still only have 1 default branch) 3. Better documentation about compatibility across this repo and the others 4. Better documentation about the purposes of the different branches in this repo
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/go-ethereum#188
No description provided.