Comment 13 for bug 1172215

On Wednesday, April 24, 2013 05:31:16 PM you wrote:
> I don't believe this decision makes sense for users.
>
> The Go port of juju is supported, maintained, and users who opt in to
> using it now will be able to avoid a painful migration later.
>
> Since this is fully opt-in, there is no advantage to waiting for
> backports to pull it in. It is a stand-alone package so will by
> definition not break anything else on the system. And having it in
> backports requires multiple steps of to get the package, enables a bunch
> of packages most server admins won't want, and thus requires pinning to
> get go juju.

It requires no extra steps.