Currently juju-reports has a rule matching on failures where our CI
harness interrupted the test because it took too long:
http://reports.vapour.ws/releases/rules/2
This seems too generic a symptom, generally if a test is not
completing within the time we've allocated for it, there's another
# juju-core 1.24-beta6
A new development release of Juju, juju-core 1.24-beta6, is now available.
This release replaces version 1.24-beta5.
## Getting Juju
juju-core 1.24-beta6 is available for vivid and backported to earlier
series in the following PPA:
On Thu, Jun 4, 2015 at 3:29 PM, Edward Hope-Morley
edward.hope-mor...@canonical.com wrote:
Ahoy Charmers!
Please consider my application for membership to
http://launchpad.net/~charmers
I looked again into the charmers team expecting to see your name ,
and I was surprised for not seeing you
# juju-core 1.22.5
A new stable release of Juju, juju-core 1.22.5, is now available.
This release replaces version 1.22.1.
Juju 1.22.x is an older supported version of juju. The current Juju
version is 1.23.3
## Getting Juju
juju-core 1.22.5 is available for vivid and backported to earlier
Hello Charmers!
A wikified version of my credentials can be found here:
https://wiki.ubuntu.com/AdamIsrael
The slightly shorter version:
I've been working with and contributing to the Juju ecosystem for a
little less than a year now. In that time, I've been a valued member of
the team,
