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. What is the case against inclusion now? Just that it is new? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172215 Title: [FFe] Please include juju-core 1.10.0 in Ubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1172215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
