I would say the exact opposite. We *cannot* sacrifice the usability and
reliability of the product for all our future users just to keep a few
current users from having to update their scripts ever.
I am sure there will come a day when we decide that there is a change that
makes the client signifi
I don't want to bore on and on about this, but one thing.
On 30 April 2015 at 22:06, Nate Finch wrote:
> If someone needs 1.18 CLI compatibility, they can use 1.18. It's that
> simple.
It's not that simple to do that though, as long as new versions of
juju go into trusty-updates. You'd have to
cp juju juju-1.18
On Thu, Apr 30, 2015 at 6:29 AM, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
> I don't want to bore on and on about this, but one thing.
>
> On 30 April 2015 at 22:06, Nate Finch wrote:
> > If someone needs 1.18 CLI compatibility, they can use 1.18. It's that
>
At the Nuremberg sprint, I saw a demo of juju status that produced
tabular format
by default. I'm guessing that this issue means that can never actually be
enabled.
Although... it could be done backwardly compatibly (with a required environment
variable or configuration file setting) and perhaps t
Right now, the default tabular output is behind a feature flag because it's
experimental. We still need to decide how to allow users to have that output by
default without the feature flag, but also without breaking 1.18 script
compatibility. The best option IMO for this case is an env variable on
On 30 April 2015 at 11:55, Ian Booth wrote:
> Right now, the default tabular output is behind a feature flag because it's
> experimental. We still need to decide how to allow users to have that output
> by
> default without the feature flag, but also without breaking 1.18 script
> compatibility.
On 30/04/15 21:04, roger peppe wrote:
> On 30 April 2015 at 11:55, Ian Booth wrote:
>> Right now, the default tabular output is behind a feature flag because it's
>> experimental. We still need to decide how to allow users to have that output
>> by
>> default without the feature flag, but also
On Thu, 30 Apr 2015, Nate Finch wrote:
> If someone needs 1.18 CLI compatibility, they can use 1.18. It's that
> simple. We're maintaining API compatibility for just this reason. If they
> don't want the binary to change, they shouldn't update it (or should just
> rename it to juju-1.18 or some
# juju-core 1.23.2
A new stable release of Juju, juju-core 1.23.2, is now available.
This release replaces version 1.22.1.
## Getting Juju
juju-core 1.23.2 is available for vivid and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/stable
Windows and
\o/
Thanks for the hard work on this. I can't wait to give all these new
features a spin.
-Antonio
On Thu, Apr 30, 2015 at 8:41 PM, Curtis Hovey-Canonical
wrote:
> # juju-core 1.23.2
>
> A new stable release of Juju, juju-core 1.23.2, is now available.
> This release replaces version 1.22.1.
>
10 matches
Mail list logo
