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 classic
latest/candidate: 2.2-rc2 (1929) 25MB classic
latest/beta: 2.2-rc2 (1929) 25MB classic
latest/edge: 2.3-alpha1+develop-1cb9c09 (1933) 42MB classic
Nicholas
On 06/12/2017 12:17 PM, Jason Hobbs wrote:
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 <mailto: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 now
are being published again.
Nicholas
On 06/12/2017 11:18 AM, Jason Hobbs wrote:
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: 2.2-rc1 (1925) 25MB classic
edge: 2.2-rc1+develop-7256fe0 (1915) 44MB classic
Thanks,
Jason
On Fri, Jun 9, 2017 at 6:25 AM, Chris Lee
<chris....@canonical.com <mailto:chris....@canonical.com>
<mailto:chris....@canonical.com
<mailto:chris....@canonical.com>>> wrote:
# 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 MacOS client, and adds support for repeatable spell
deployments.
The best way to get your hands on this release of Juju and
conjure-up is to install them via snap packages (see
https://snapcraft.io/for more info on snaps).
snap install juju --classic --candidate
snap install conjure-up --classic --candidate
Other packages are available for a variety of platforms.
Please
see the online documentation at
https://jujucharms.com/docs/devel/reference-releases#development
<https://jujucharms.com/docs/devel/reference-releases#development>
<https://jujucharms.com/docs/devel/reference-releases#development
<https://jujucharms.com/docs/devel/reference-releases#development>>
Please note that if you are upgrading an existing controller,
please make sure there is at least 6G of free disk space. The
upgrade step for the logs can take a while, in the
vicinity of 10
or more minutes if the current logs collection is at its
maximum size.
Since 2.2-rc1
## New and Improved
------------------------------------------------------------------------
Better support credential management in the Azure provider
* support autoload-credentials and juju add-credential in the
azure provider when Azure CLI is installed.
(this removes the requirement that the user discover their
subscription ID before creating credentials)
Rate limit login and connection requests to the
controller(s) on
busy systems.
## Fixes
------------------------------------------------------------------------
Fix issue where status history logs were not pruned:
https://bugs.launchpad.net/juju/+bug/1696491
<https://bugs.launchpad.net/juju/+bug/1696491>
<https://bugs.launchpad.net/juju/+bug/1696491
<https://bugs.launchpad.net/juju/+bug/1696491>>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com <mailto:Juju-dev@lists.ubuntu.com>
<mailto:Juju-dev@lists.ubuntu.com
<mailto:Juju-dev@lists.ubuntu.com>>
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
<https://lists.ubuntu.com/mailman/listinfo/juju-dev>
<https://lists.ubuntu.com/mailman/listinfo/juju-dev
<https://lists.ubuntu.com/mailman/listinfo/juju-dev>>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
