"environment" vs "model" in the code

[roger peppe]

On 20 January 2016 at 10:52, William Reade <william.reade at canonical.com> wrote:
> On Wed, Jan 20, 2016 at 4:19 AM, Ian Booth <ian.booth at canonical.com> 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, associated text, api parameters etc - the
>> outwardly facing artifacts. I'm sure we can all deal with a little
>> inconsistency
>> for a short time. There will be inconsistency anyway with the current in
>> progress work.
>
>
> Yeah, we can't dodge some degree of inconsistency, whatever we do; and every
> env-thing in the code might *already* refer to either an environment (which
> should be renamed) or an environ (which should not).

FWIW, type-aware renaming can cope with the above ambiguity.