On Wed, Feb 24, 2016 at 10:47 PM, Henrik Lindberg <
henrik.lindb...@puppetlabs.com> wrote:
> On 23/02/16 01:47, Henrik Lindberg wrote:
>
>> Hi, I am thinking ahead a bit regarding puppet 5 and how we should deal
>> with all the requests for features that require deprecations. (There are
>> some re
On 23/02/16 01:47, Henrik Lindberg wrote:
Hi, I am thinking ahead a bit regarding puppet 5 and how we should deal
with all the requests for features that require deprecations. (There are
some related things like requests for additional validation and warnings
that are different from deprecations)
On 24/02/16 20:24, Walter Heck wrote:
On Wednesday, February 24, 2016 at 11:49:17 AM UTC+1, Trevor Vaughan wrote:
I'm also a fan of per module which can override a global setting.
If it could be part of the metadata.json, that would be ideal and
would allow for attestation on the Fo
We've stopped using the rolling release names (stable, testing) for our
Debian packages and instead use the direct codenames. This maps better to
our processes and is more maintainable over time. What this means is that
the stable/testing portions of the apt repos will be removed. All packages
will
+1 to the mode support in the metadata.json
Dependency checking will be more fun.
Trevor
On Wed, Feb 24, 2016 at 2:24 PM, Walter Heck
wrote:
> On Wednesday, February 24, 2016 at 11:49:17 AM UTC+1, Trevor Vaughan wrote:
>>
>> I'm also a fan of per module which can override a global setting.
>>
On Wednesday, February 24, 2016 at 11:49:17 AM UTC+1, Trevor Vaughan wrote:
>
> I'm also a fan of per module which can override a global setting.
>
> If it could be part of the metadata.json, that would be ideal and would
> allow for attestation on the Forge if appropriate.
>
I gave this some thou
On Wed, Feb 24, 2016 at 5:58 AM, Henrik Lindberg
wrote:
> On 24/02/16 11:49, Trevor Vaughan wrote:
>>
>> I'm also a fan of per module which can override a global setting.
>>
>> If it could be part of the metadata.json, that would be ideal and would
>> allow for attestation on the Forge if appropri
On 24/02/16 11:49, Trevor Vaughan wrote:
I'm also a fan of per module which can override a global setting.
If it could be part of the metadata.json, that would be ideal and would
allow for attestation on the Forge if appropriate.
The global --strict=off should override any module-level setting.
I'm also a fan of per module which can override a global setting.
If it could be part of the metadata.json, that would be ideal and would
allow for attestation on the Forge if appropriate.
The global --strict=off should override any module-level setting.
Thanks,
Trevor
On Tue, Feb 23, 2016 at
