As Bret points out, a channel is really formed by the tuple (track, risk, branch), where the branch is optional and track defaults to latest, per our agreements and the documentation.
As such, there’s nothing wrong in having:
- multiple risks and same track: 1.0/stable + 1.0/candidate
- multiple tracks and same risk: 1.0/stable + 2.0/stable
- multiple risks and same branch: stable/fix-one + beta/fix-one
- multiple branches and same risk: stable/fix-one + stable/fix-two
and so on.