v0.6 was released, which is just bzr592 + the version bump. ** Summary changed:
- [FFe] Please update to new snapshot release ~bzr592 + [FFe] Please update to new release 0.6 ** Description changed: - The latest updates to juju trunk include a number of bug fixes and one - major refactor which are important for quantal + The latest release from juju trunk includes a number of bug fixes and + one major refactor which are important for quantal Features: - Refactoring to Local provider to use Ubuntu Cloud Images; this resolves a number of networking issues with the local provider (removes the dependency on libvirt) and makes the local provider instances behave more like those used in cloud deployments. Two key regressions: * Regresses HTTPS apt support for local provider because cloud-init doesn't have a way to make the distinction. * Regresses performance for the case where the download is cached. rsync'ing from the debootstrap is a little faster than extracting the tar.gz. Also we now do a full apt-get upgrade, so all updates have to be unpacked/configured. - MAAS constraints; currently only machine-name is supported; this makes the MAAS provider in Juju much more useful; change in behaviour of MAAS provider so some regression potential. - Juju: Add --version option - no regression potential. Bug Fixes: - Openstack Folsom compatibility - Fix reporting of exceptions For full details see - https://code.launchpad.net/~juju/juju/trunk commits 586->592 Build log: see attached Testing: - Tested local provider with 12.04 cloud images; OK - Tested openstack provider with OpenStack Folsom: OK - Tested interoperability with existing Openstack Essex environment: OK - Tested with ec2 provider: OK ** Description changed: The latest release from juju trunk includes a number of bug fixes and one major refactor which are important for quantal Features: - Refactoring to Local provider to use Ubuntu Cloud Images; this resolves a number of networking issues with the local provider (removes the dependency on libvirt) and makes the local provider instances behave more like those used in cloud deployments. Two key regressions: * Regresses HTTPS apt support for local provider because cloud-init doesn't have a way to make the distinction. * Regresses performance for the case where the download is cached. rsync'ing from the debootstrap is a little faster than extracting the tar.gz. Also we now do a full apt-get upgrade, so all updates have to be unpacked/configured. - MAAS constraints; currently only machine-name is supported; this makes the MAAS provider in Juju much more useful; change in behaviour of MAAS provider so some regression potential. - Juju: Add --version option - no regression potential. Bug Fixes: - Openstack Folsom compatibility - Fix reporting of exceptions For full details see - https://code.launchpad.net/~juju/juju/trunk - commits 586->592 + commits 586->594 Build log: see attached Testing: - Tested local provider with 12.04 cloud images; OK - Tested openstack provider with OpenStack Folsom: OK - Tested interoperability with existing Openstack Essex environment: OK - Tested with ec2 provider: OK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063697 Title: [FFe] Please update to new release 0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1063697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
