On 20 January 2016 at 10:52, William Reade wrote:
> On Wed, Jan 20, 2016 at 4:19 AM, Ian Booth wrote:
>>
>> I'm a firm -1 to using old terminology for new work.
>>
>> Doing anything other than using the new terminology for new work is simply
>> kicking the can down the road. We don't have time fo
On Mon, Jan 18, 2016 at 8:24 PM, Rick Harding
wrote:
> No, there's not been a public note yet. It's work going into the 2.0
> updates currently.
>
> The gist of the reason is that as support for things such as networking,
> storage, and workloads expand out the idea is that Juju is doing more to
On Wed, Jan 20, 2016 at 4:19 AM, Ian Booth wrote:
> I'm a firm -1 to using old terminology for new work.
>
> Doing anything other than using the new terminology for new work is simply
> kicking the can down the road. We don't have time for re-work. We are
> currently
> undetaking the rename of CL
On 20 January 2016 at 16:19, Ian Booth wrote:
> I'm a firm -1 to using old terminology for new work.
>
> Doing anything other than using the new terminology for new work is simply
> kicking the can down the road. We don't have time for re-work. We are
> currently
> undetaking the rename of CLI, a
I'm a firm -1 to using old terminology for new work.
Doing anything other than using the new terminology for new work is simply
kicking the can down the road. We don't have time for re-work. We are currently
undetaking the rename of CLI, associated text, api parameters etc - the
outwardly facing a
No, there's not been a public note yet. It's work going into the 2.0
updates currently.
The gist of the reason is that as support for things such as networking,
storage, and workloads expand out the idea is that Juju is doing more to
model your infrastructure and workloads vs an environment. So fa
out of curiosity is there any public explanation on the reason for the
change? environments map fairly naturally to various service topology
stages, ie my prod, qa, dev environments. while model is a rather opaque
term that doesn't convey much.
On Thu, Jan 14, 2016 at 7:16 PM, Menno Smits
wrote:
Menno
Ian is traveling, so the renaming discussion will take place when he is
back online full-time - most likely Wednesday for us...
Renames scheduled for this iteration are:
* CLI;
* user facing text;
* api facades [methods and parameter names].
This is scheduled for this Iteration but we all
+1 to what Roger said. New features always require changes to existing code
so inconsistency is unavoidable if we take a piecemeal approach.
Given that a big rename is planned at some point, and that renaming can be
largely automated, continuing to use "environment" internally until the big
rename
On 15 January 2016 at 06:03, Ian Booth wrote:
>
>
> On 15/01/16 10:16, Menno Smits wrote:
>> Hi all,
>>
>> We've committed to renaming "environment" to "model" in Juju's CLI and API
>> but what do we want to do in Juju's internals? I'm currently adding
>> significant new model/environment related
On 15/01/16 10:16, Menno Smits wrote:
> Hi all,
>
> We've committed to renaming "environment" to "model" in Juju's CLI and API
> but what do we want to do in Juju's internals? I'm currently adding
> significant new model/environment related functionality to the state
> package which includes add
Hi all,
We've committed to renaming "environment" to "model" in Juju's CLI and API
but what do we want to do in Juju's internals? I'm currently adding
significant new model/environment related functionality to the state
package which includes adding new database collections, structs and
functions
12 matches
Mail list logo