-
Notifications
You must be signed in to change notification settings - Fork 60
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
(name to be decided) routing topology #411
Comments
adamralph
changed the title
New (name to be decided) routing topology
(name to be decided) routing topology and required topology choice
Sep 1, 2017
This was referenced Sep 1, 2017
adamralph
changed the title
(name to be decided) routing topology and required topology choice
(name to be decided) routing topology
Sep 5, 2017
Requiring a topology choice has been split off into #427 which means this issue no longer requires a breaking change. It remains on the 5.0.0 milestone for now, but we have the option to deliver it in a later (minor) version instead. |
What is this about? No info at all about this topology. What things are addressed. Is this info present somewhere? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Depends on #427.
The current default routing topologies (conventional and direct) have problems that could only solved by breaking wire compatibility. Rather than do that, we will deprecate the current routing topologies and introduce a new one which does not have those problems.
Plan of attack
The text was updated successfully, but these errors were encountered: