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.

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

Split and migrate origin/bridges-v2 branch #2976

Open
bkontur opened this issue May 2, 2024 · 0 comments · May be fixed by paritytech/polkadot-sdk#4427
Open

Split and migrate origin/bridges-v2 branch #2976

bkontur opened this issue May 2, 2024 · 0 comments · May be fixed by paritytech/polkadot-sdk#4427
Assignees

Comments

@bkontur
Copy link
Contributor

bkontur commented May 2, 2024

origin/bridges-v2 contains dynamic lanes stuff, so we need to migrate it:

  • relayer-relevant changes stays in bridges repo above master branch
  • runtime-relevant changes goes to the polkadot-sdk repo above master branch

Possible solution 1:

  • refactor origin/bridges-v2 so it reflects actual bridges master structure for relayer code
    • rebase or merge with latest master
    • remove all runtime-relevant code
    • origin/bridges-v2-relayer
  • refactor origin/bridges-v2 so it reflects actual polkadot-sdk master structure for runtime code in ./bridges substree
    • migrate cleaned-up branch to the polkadot-sdk above actual master
      • remove or ignore relayer-related code
      • origin/bridges-v2-runtime

Possible solution 2:

  • maybe just cherry-pick all commits from origin/bridges-v2 manually ignoring those with bumping crates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant