[Bug 1506652] Re: [needs-packaging] Juju 1.24.7 is not in Ubuntu

[Curtis Hovey]

** Description changed:

  Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
  the m1* instance types and users of older Jujus are seeing cases where
  EC2 does not have enough instances. Juju 1.24.7 will ask for newer
  instance types. Juju 1.24.7 has a dhcp related fix to work with MAAS
  1.9.
  
  [SRU Information]
  
  juju-core has a stable release exception in
  https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
  including for major version updates.
  
  [Devel Fix]
  
  [sinzui] Prepare source package and diffs: DONE
  [rbasak] Review package and upload of new upstream release with packaging review: TODO
  
  [Stable Fix]
  
  [sinzui] backport wily source package and prepare diffs for vivid: DONE
  [rbasak] Review package for vivid-proposed: DONE
  [sinzui] backport source package and prepare diffs for trusty: DONE
  [rbasak] Review package for trusty-proposed: DONE
  
  [Pre-QA tasks]
  
  [rbasak] Upload to the current supported release (vivid-proposed): DONE
  [rbasak] Upload to the current LTS release (trusty-proposed): DONE
  
  [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-TODO 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 Vivid: DONE
- [sinzui] Upstream QA test against Trusty: TODO
+ [sinzui] Upstream QA test against Trusty: DONE
  [sinzui] Upstream release process complete: DONE
  
  Manual tests required:
  
  [sinzui] Test juju-quickstart against vivid-proposed: DONE
  [sinzui] Test juju-deployer against vivid-proposed: DONE
  [sinzui] Test client and cloud server upgrade against vivid-proposed: DONE
  [sinzui] Test client manual bootstrap and add-machine against vivid-proposed: DONE
  
- [sinzui] Test juju-quickstart against trusty-proposed: TODO
- [sinzui] Test juju-deployer against trusty-proposed: TODO
- [sinzui] Test client and cloud server upgrade against trusty-proposed: TODO
- [sinzui] Test client manual bootstrap and add-machine against trusty-proposed: TODO
+ [sinzui] Test juju-quickstart against trusty-proposed: DONE
+ [sinzui] Test juju-deployer against trusty-proposed: DONE
+ [sinzui] Test client and cloud server upgrade against trusty-proposed: DONE
+ [sinzui] Test client manual bootstrap and add-machine against trusty-proposed: DONE

** Description changed:

  Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
  the m1* instance types and users of older Jujus are seeing cases where
  EC2 does not have enough instances. Juju 1.24.7 will ask for newer
  instance types. Juju 1.24.7 has a dhcp related fix to work with MAAS
  1.9.
  
  [SRU Information]
  
  juju-core has a stable release exception in
  https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
  including for major version updates.
  
  [Devel Fix]
  
  [sinzui] Prepare source package and diffs: DONE
- [rbasak] Review package and upload of new upstream release with packaging review: TODO
+ [rbasak] Review package and upload of new upstream release with packaging review: DONE
  
  [Stable Fix]
  
  [sinzui] backport wily source package and prepare diffs for vivid: DONE
  [rbasak] Review package for vivid-proposed: DONE
  [sinzui] backport source package and prepare diffs for trusty: DONE
  [rbasak] Review package for trusty-proposed: DONE
  
  [Pre-QA tasks]
  
  [rbasak] Upload to the current supported release (vivid-proposed): DONE
  [rbasak] Upload to the current LTS release (trusty-proposed): DONE
  
  [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-TODO 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 Vivid: DONE
  [sinzui] Upstream QA test against Trusty: DONE
  [sinzui] Upstream release process complete: DONE
  
  Manual tests required:
  
  [sinzui] Test juju-quickstart against vivid-proposed: DONE
  [sinzui] Test juju-deployer against vivid-proposed: DONE
  [sinzui] Test client and cloud server upgrade against vivid-proposed: DONE
  [sinzui] Test client manual bootstrap and add-machine against vivid-proposed: DONE
  
  [sinzui] Test juju-quickstart against trusty-proposed: DONE
  [sinzui] Test juju-deployer against trusty-proposed: DONE
  [sinzui] Test client and cloud server upgrade against trusty-proposed: DONE
  [sinzui] Test client manual bootstrap and add-machine against trusty-proposed: DONE

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1506652

Title:
  [needs-packaging] Juju 1.24.7 is not in Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1506652/+subscriptions