Hi folks,
Due to a change I landed without fully thinking through the
implications, the reverting of said change has pushed us out a day.
I was trying to add consistency to the wire-protocol that Juju uses by
changing the serialisation names. Thinking that we were still in the "we
don't need no backward compatibility phase" I made this change without
bumping the facade versions. This would have broken all the API users.
This is what we are backing out.
Sorry for the inconvenience.
Tim
On 15/06/16 12:19, Cheryl Jennings wrote:
Hi Everyone,
Due to a critical bug [0] found in the daily PPA, the release of
2.0-beta9 will be delayed while we test the fix. We are aiming for a
release tomorrow.
Thanks!
-Cheryl
[0] https://bugs.launchpad.net/juju-core/+bug/1592210
On Fri, Jun 10, 2016 at 1:20 PM, Cheryl Jennings
<cheryl.jenni...@canonical.com <mailto:cheryl.jenni...@canonical.com>>
wrote:
The team has been busily working on 2.0-beta9 with an aim to address
usability feedback and ensure that beta9 will be upgradeable to
subsequent releases. Ensuring upgradeability has required a
significant amount of work to finalize internal details, and the
team needs a few extra days to make sure this work is completed.
To achieve this guarantee, we are moving the expected date for
2.0-beta9 to Tuesday, June 14.
Some of the great things coming in beta9 include:
- Renaming of 'service' to 'application' to better align terminology
- Shortened instance IDs for the lxd provider (ex: 'juju-622af3-0')
- Addition of a `juju unregister` command to remove references to
controllers
- Separation of controller config vs. model config
- Improved status output
- Numerous bug fixes
There is an early beta9 available in the juju daily ppa
(ppa:juju/daily) for those who wish early access to the above features.
If you have any questions, please let me know.
Thanks!
-Cheryl
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
