tl;dr Juju 2.0 has moved to lp:juju vs lp:juju-core, please make sure to file bugs and track blueprints there.
The Juju team is getting ready for Juju 2.0 and as part of that work, we’ve moved the Juju 2.0 project in launchpad to the launchpad.net/juju namespace. All 2.0 bugs, blueprints, and future milestones are moved to the new project name. Juju 2.0 is so different from Juju 1.X that many of the old issues and blueprints no longer apply. To help us provide some clarity on things that carry over, we’ve migrated bugs that we could clearly identify as 2.0 wishlist and issues to the lp:juju project. If you believe we did not migrate a bug that still applies to 2.0 then please make sure to update the project it affects. The team is focused on polishing Juju 2.0 before release and to help the team focus on that we are making Juju 1.25 a critical only bugfix release. We will support it until Trusty EOL’s but only for issues that are deemed a critical. Make sure that you add your bug subscriptions to the new project in order to continue to get the email updates that you’re expecting. Head over to https://bugs.launchpad.net/juju and select "Subscribe to bug mail". From there you can adjust the bugs notifications you get. If you have any questions or concerns please don’t hesitate to ask. Rick
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
