Comment 0 for bug 1500916

Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to Vivid do not get a downgrade that looses
bug fixes.

See bug 1481556 for the history of placing juju-core 1.24.6 into Wily.

[SRU Information]

juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version
updates.

[Vivid Fix]

[sinzui] Prepare source package, and diffs: TODO
[rbasak] Review package and upload of new upstream release with packaging review.

[Pre-QA tasks]

[rbasak] Upload to the development release (vivid-proposed): TODO

[QA Status]

Since there are multiple verifications required, they are listed here as a work
item whiteboard status type thing rather than try and track them in a single
tag. Please do not mark verification-done or remove block-proposed until all
following items have passed. If any of these items fail, this bug should be
marked verification-failed immediately.

[sinzui] Upstream release process complete: DONE
[sinzui] Upstream QA test against Vivid: TODO

Manual tests required:

[sinzui] Test juju-quickstart against wily-proposed: TODO
[sinzui] Test juju-deployer against wily-proposed: TODO
[sinzui] Test client and cloud server upgrade from main/updates: TODO
[sinzui] Test client manual bootstrap and add-machine: TODO