Yes, and this too has been corrected. You should expect releases to flow
down to level of risk. So, when 2.2 releases, beta, candidate and stable
will all point to the 2.2 revision (until the first beta for 2.3, and so
on).
channels:
latest/stable:2.1.3 (1922) 24MB
Nicholas,
Thanks. beta is still 2.2rc1. Should it be 2.2rc2 also?
Jason
On Mon, Jun 12, 2017 at 11:15 AM, Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:
> Thanks for the heads-up Jason. Yes, small snafu with publishing the
> builds. Edge builds are tracking develop (2.3-alpha1) and
I noticed that for the juju snap, edge and beta channels have older
releases than candidate. Shouldn't they always be at least the same
version as candidate, if not newer?
stable:2.1.3 (1922) 24MB classic
candidate: 2.2-rc2 (1929) 25MB classic
beta:
On Fri, Jun 9, 2017 at 12:29 PM, Uros Jovanovic <
uros.jovano...@canonical.com> wrote:
> Quick instructions on how the new azure credentials flow works in Juju
> 2.2-RC2:
>
> # install az client using a snap
> $ sudo snap install azure-cli --classic --edge
>
I've pushed the snap to stable, so
# Juju 2.2-rc2 Release Notes
We are delighted to announce the release of Juju and conjure-up 2.2-rc2! In
this release, Juju greatly improves memory and storage consumption, works
on KVM containers, and improves network modelling. conjure-up now supports
Juju as a Service (JAAS), provides a
