On 12 March 2015 at 07:22, Andrew Wilkins andrew.wilk...@canonical.com wrote:
On Thu, Mar 12, 2015 at 2:53 PM, Tim Penhey tim.pen...@canonical.com
wrote:
On 12/03/15 18:13, Ian Booth wrote:
I see the point. But it could be considered analogous to having lots of
methods
called New() etc.
Note that 'go fmt' isn't the only one confused by this.
go test also gives incorrect paths:
$ cd $HOME/jc/worker/uniter/relation
$ go build
../../../../dev/go/src/
github.com/juju/juju/worker/uniter/relation/livesource.go:130: undefined:
change
However ../ is actually evaluated relative to the
On 12/03/15 05:01, David Cheney wrote:
lucky(~/src/github.com/juju/juju) % pt -i type\ State\ | wc -l
23
Thank you.
When I was new to Juju the fact that we had a central State, core to
the Juju model, but we had umpteen types called State - so where you saw
a State you had no idea what
Perhaps a better solution would have been a better name for the core State.
Michael
+
1
Also matches my sprint topic about an improved management of our
persistency (separation of model types and interfaces for their
persistency; grouped by domains; instantiated by factories to allow
When I was new to juju myself, we only had one State, I believe. That
one golden state was supposed to represent the state of the whole
deployment, so it was indeed The State of the system. Having tons of
these indeed sounds awkward.
On Thu, Mar 12, 2015 at 8:08 AM, Michael Foord
We branch juju master at commit 5b193d8 to create 1.23
https://github.com/juju/juju/commits/1.23
http://reports.vapour.ws/releases/2441
Master was one commit ahead of the blessed commit. Dimiter will
backport that change to 1.23.
If you have a fix for 1.23, please merge into 1.23 first,
On 12 March 2015 at 14:23, Gustavo Niemeyer gust...@niemeyer.net wrote:
The core state (The State) is the one case where it doesn't matter,
IMO. Everybody knows what it is. It's the other dozen that create the
issue, and they will remain as ambiguous if you just rename the one
State.
The
Hello,
I'm happy to announce the Amulet 1.10.0 release. You can install and
upgrade amulet from the juju stable ppa:
sudo add-apt-repository ppa:juju/stable
sudo apt-get update
sudo apt-get install amulet
For all other users, amulet is available in pip
pip install amulet
#
# juju-core 1.22.0
A new proposed stable release of Juju, juju-core 1.22.0, is now available.
This release may replace 1.21.3 on Thursday March 19, 2015.
## Getting Juju
juju-core 1.22.0 is available for utopic and backported to earlier
series in the following PPA:
# juju-core 1.22.0
A new proposed stable release of Juju, juju-core 1.22.0, is now available.
This release may replace 1.21.3 on Thursday March 19, 2015.
## Getting Juju
juju-core 1.22.0 is available for utopic and backported to earlier
series in the following PPA:
Hi All,
systemd support in juju has been developed and currently is in trunk. It
will be available in the 1.23 release scheduled to go beta next week.
Upstart will continue to be supported as well. However, versions of juju
prior to 1.23 will not support systemd. This means that these versions
On 12/03/15 18:13, Ian Booth wrote:
I see the point. But it could be considered analogous to having lots of
methods
called New() etc. So long as the types are relevant for the package in which
they're declared then isn't that ok? If we have lots of packages where state
needs to be persisted,
On 12/03/15 16:53, Tim Penhey wrote:
On 12/03/15 18:13, Ian Booth wrote:
I see the point. But it could be considered analogous to having lots of
methods
called New() etc. So long as the types are relevant for the package in which
they're declared then isn't that ok? If we have lots of
13 matches
Mail list logo
