At some point, we will move to zipkin 2.0. That would imply making a maintenance branch 1.x
I don't know what might break when we do that, but it is probably safe to assume stuff is optimized for releasing from master. Let's make sure that we can release from another branch before we move our version to 2.
cc @openzipkin/devops-tooling there's no schedule for 2.x, which is good because that means no immediate time pressure for this. That said, it will become needed probably within a month or two.