Comment 17 for bug 1545913

These updates were presented to slangasek and the point of the making juju1 the default is the one point left that we requested feedback on.

Feedback from slangasek is that if we're not prepared to make juju1 the default then:
"upon upgrade, juju == juju2; if you want juju1, run juju-1.$fwibble instead"

The Juju team defers to the distro team in regards to Juju upgrades and will move forward with this plan during updates and update the juju2 command such that if it detects you're a new juju2 user with existing juju1 environments.yaml file we will direct you to the new command to run as a helpful hint.

Please direct feedback on this decision to slangasek.