Comment 82 for bug 1267393

If the move to golang-yaml.v2 is low risk and can be done, then I'll include that package for MIR and drop golang-goyaml and golang-gocheck; however if that's not the case, then I think we should *not* use golang-goyaml-dev and fallback to the embedded code copy in juju-core for this cycle; juju should be able to switch in a newer release at a future date.