[ANN] juju-core 1.9.2 has been released

[David Cheney]

juju-core 1.9.2
===============

A new release of Juju, juju-core 1.9.2, is now available for testing. 
This is second release of the Go port of Juju and should be considered 
*experimental*.

Getting Juju
------------

juju-core 1.9.2 is available from the Gophers PPA

https://code.launchpad.net/~gophers/+archive/go

Required configuration changes
------------------------------

When bootstrapping an environment, juju needs to know where to download 
the matching set of tools. For EC2 environments, these are stored in a 
public S3 bucket. Please add the following configuration key to all EC2 
environments in your environments.yaml file.

	public-bucket: juju-dist

New and Notable
---------------

This release includes several improvements

* juju-core now supports bootstrapping and deploying from clients 
running either Precise or Quantal. However, the client must be running 
amd64. 386 or arm clients are not supported.
* Support has been added for EC2 ap-southeast-2 region.
* In the hope of encouraging collaborators, initial README and 
CONTRIBUTING documentation is available in the source.

Known bugs and limitations
--------------------------

As this is an early release of Juju in Go there are a number of features 
which are still to be implemented. A non exhaustive list of known issues 
is as follows.

* EC2 is the only supported provider.
* Raring series environments are not supported.
* default-series is not respected, the series of the environment will 
match the series of the machine which issued the juju bootstrap command. 
#1074064
* Most types of relations are supported, but they are not displayed in 
juju status. #1073966
* The ssl-hostname-verification configuration key is not valid in an 
environments.yaml configuration. The EC2 provider does perform ssl host 
verification by virtue of only talking to https endpoints. As a 
temporary measure, please remove this key from your environments.yaml. 
#1074025
* us-east-1 is the most reliable region to deploy into. Due to subtle 
differences in the EC2 regions, juju bootstrap may fail. The current 
workaround is to use us-east-1, retry your juju deploy command, or 
change your control bucket after destroying your previous environment. 
#1042107
* The juju-core package currently cannot be installed in parallel with 
juju 0.5/0.6 due to conflicting ownership of /usr/bin/juju (and others). 
This may be mitigated in the future with alternatives.
destroy-service is not yet implemented. As a workaround you can remove 
all the units assigned to a service. This is issue #1027878.
terminate-machine is not yet implemented. #1073976
* Constraints are not yet implemented. #1027873
* Subordinate charms are not yet implemented.

We encourage everyone to subscribe the mailing list at 
juju-dev at lists.canonical.com, or join us on #juju-dev on freenode.

Dave Cheney
On behalf of the Juju team
https://launchpad.net/juju-core