Comment 16 for bug 1545913

- adding a comment to the juju 2.0 FFe that clarifies that the juju client is built and runs on all architectures, including 32bit.

Comment added under the heading Mongodb to this effect since that's where the confusion derived from.

- document the process for avoiding a late stage FFe and package upload for 16.10

Added section to the FFe under the heading "Future release planning"

- move the juju binary metapackage suggest juju-1.25 so that upgrades will make sure that juju 1 stays available

This change is made and new builds are being done.

- make juju1 the higher update-alternatives priority.

We cannot make this change due to direction from product management. We have filed this for record under https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564670.

We've also created the Juju bug to perform the update that outputs the mitigating messaging to help the user in the 2.0 Juju.
https://bugs.launchpad.net/juju-core/+bug/1564622

- trim the binary size of the juju package by reducing the duplication

See bug https://bugs.launchpad.net/juju-core/+bug/1564677 for the work to perform this. This will be a goal of the next full release to perform this action to reduce the Juju binary size.

- investigate the ability to perform stripping to reduce size

See bug https://bugs.launchpad.net/juju-core/+bug/1564662 for this work. This will be a goal for the next full release to perform this action and reduce the Juju binary size. However, we need time to validate that it is 100% safe and we feel the risk is too high to push it through today.