-
Notifications
You must be signed in to change notification settings - Fork 131
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
Drop Rialto <> Millau bridges #2663
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@svyatonik Slava, you should write some condolence speech for Millau and Rialto :(,
Maybe I asked that before, but who and why did choose those names?
Will do the same for `polkadot-staging?
Let's just move forward with that. I think @tomusdrw was behind that :) Just some bridges (https://en.wikipedia.org/wiki/Rialto_Bridge + https://en.wikipedia.org/wiki/Millau_Viaduct) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
40K lines fewer to maintain ❤️
Indeed :) |
* drop Rialto <> Millau bridges * clippy
* drop Rialto <> Millau bridges * clippy
* drop Rialto <> Millau bridges * clippy
* drop Rialto <> Millau bridges * clippy
We already have some troubles with maintaining those bridges (#2647 (review)).
Since we already have a live setup (Rococo <> Wococo), which will be superseded with Rococo <> Westend bridge soon AND at least we have some basic zombienet tests, I think the time has come to drop Rialto and Millau (and test deployments VM).
Couple of things to mention:
substrate-relay
binary;polkadot-sdk
;substrate-relay
binary. We'll need to have a similar build step inpolkadot-sdk
, but until that, we'll be building it from here.