Comment 0 for bug 1462001

We're now in a position to have 1.22.5 enter trusty-proposed.

[SRU Information]

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

[Development Fix]

Upload of new upstream release with packaging review. [<person>] will remove the block-proposed tag when verification has passed, and then this update should migrate to trusty.

[Stable Fix]

Full backport of new upstream release.

[Pre-QA tasks]

[<person>] Upload to the current LTS release (trusty-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 QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO

Manual tests required:

[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer against trusty-proposed: TODO

The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug.

Landscape team QA: TODO