Merge master for your feature branches

Hi everyone, The admin-controller-model branch which merged into master yesterday brought the new behavior of two models being created upon bootstrap - "admin" and "default". Significant changes were needed in CI to support this new behavior. You will need to merge master into your feature

Move provider implementations under their related projects.

Perhaps we should move the implementation of some providers over to the repos for the projects with which the providers interact (and then just import them in providers/all). Then those providers would be more likely to stay up-to-date in the face of changes in the project, particularly

Collection of Juju talks and presentations

Hello everyone, We've revamped the old central collection of Juju slides and talks: https://github.com/juju/juju-talks If you want to toss in your slides for any talks (Eco and core) please submit a PR. I've also added a section for topics and titles for things we've submitted to conferences.

Collection of Juju talks and presentations

Hello everyone, We've revamped the old central collection of Juju slides and talks: https://github.com/juju/juju-talks If you want to toss in your slides for any talks (Eco and core) please submit a PR. I've also added a section for topics and titles for things we've submitted to conferences.

Re: Go 1.6 is now in trusty-proposed

On 24/03/2016, Ian Booth wrote: > > Not yet. The builders and test infrastructure all need to be updated, and > the package needs a week to transition out of proposed. I'd also encourage people to look again at the go 1.5/1.6 unit test intermittent failures, as we're

Re: Go 1.6 is now in trusty-proposed

On 24/03/16 22:01, Nate Finch wrote: > Does this mean we can assume 1.6 for everything from now on, or is there > some other step we're waiting on? I have some code that only needs to > exist while we support 1.2, and I'd be happy to just delete it. > Not yet. The builders and test

Re: Go 1.6 is now in trusty-proposed

Does this mean we can assume 1.6 for everything from now on, or is there some other step we're waiting on? I have some code that only needs to exist while we support 1.2, and I'd be happy to just delete it. On Thu, Mar 24, 2016, 4:07 AM Tim Penhey wrote: > Awesome

Re: Go 1.6 is now in trusty-proposed

Awesome news Michael. Thank you for all your work on this. Tim On 24/03/16 19:03, Michael Hudson-Doyle wrote: > Hi, > > As of a few minutes ago, there is now a golang-1.6 package in > trusty-proposed: > https://launchpad.net/ubuntu/trusty/+source/golang-1.6 (thanks for the > review and copy,

Re: Go 1.6 is now in trusty-proposed

OMFG that is the best news. We can finally get the Juju LXD provider working properly on trusty :-D And first class support for all architectures etc :-D And no more chasing gccgo issues :-D Thanks Michael and whoever else helped make this possible. On 24/03/16 16:03, Michael Hudson-Doyle wrote:

Re: Go 1.6 is now in trusty-proposed

Thanks :) Oh yeah, https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1536882 currently has the verification-needed tag -- it would be awesome if someone (tm) could do some package builds against this version of the package -- would seem to me to be the ideal SRU verification for getting

Re: Go 1.6 is now in trusty-proposed

THIS IS FANTASTIC NEWS MICHAEL! On Thu, Mar 24, 2016 at 5:03 PM, Michael Hudson-Doyle wrote: > Hi, > > As of a few minutes ago, there is now a golang-1.6 package in > trusty-proposed: > https://launchpad.net/ubuntu/trusty/+source/golang-1.6 (thanks for the > review

Go 1.6 is now in trusty-proposed

Hi, As of a few minutes ago, there is now a golang-1.6 package in trusty-proposed: https://launchpad.net/ubuntu/trusty/+source/golang-1.6 (thanks for the review and copy, Steve). One difference between this and the package I prepared earlier is that it does not install /usr/bin/go but rather