Re: [Puppet-dev] Re: Idea: Deprecation logs

I created https://tickets.puppetlabs.com/browse/PUP-6169 for those who want to watch/vote/comment further. Thanks everyone! Rob Nelson rnels...@gmail.com On Sun, Apr 10, 2016 at 9:16 PM, Rob Nelson wrote: > On Sun, Apr 10, 2016 at 5:05 AM, Alex Harvey wrote > >> >> On 10 April 2016 at 03:59,

Re: [Puppet-dev] Re: Idea: Deprecation logs

On Sun, Apr 10, 2016 at 5:05 AM, Alex Harvey wrote > > On 10 April 2016 at 03:59, R.I.Pienaar wrote: >> >> >> Not really sure I follow most of this rant. >> > > Yes, fair enough. It was a bit of an uncalled-for rant. > I think it's a legitimate concern. That's why I brought this up. Being surp

[Puppet-dev] Re: Idea: Deprecation logs

Am 11.04.2016 um 00:47 schrieb James Turnbull: >> One last very important factor to the mentioned frustration is the fact >> that Puppet is an Open Source product. People over here in Europe see >> this stricter than they might in the US. If you say "...and it has an >> Enterprise version", 99% of

[Puppet-dev] Re: Idea: Deprecation logs

Hi Eric! Am 10.04.2016 um 21:16 schrieb Eric Sorenson: > On Apr 10, 2016, at 2:05 AM, Alex Harvey > wrote: > > [...] I've been the product manager for Puppet for the > four years you're talking about and thus bear at least partial > responsibility for the changes in

Re: [Puppet-dev] Re: Idea: Deprecation logs

> One last very important factor to the mentioned frustration is the fact > that Puppet is an Open Source product. People over here in Europe see > this stricter than they might in the US. If you say "...and it has an > Enterprise version", 99% of the time "Oh, so it isn't really open?" is > the re

[Puppet-dev] Re: Idea: Deprecation logs

I feel a little bit guilty, as my short comment somehow started this thread. But as the discussion seems to move to a good direction, let me jump in :) Am 10.04.2016 um 18:51 schrieb R.I.Pienaar: >> I guess what this shows is that even when changes don't appear to be >> user-impacting, they are. [

Re: [Puppet-dev] Re: Idea: Deprecation logs

- Original Message - > From: "Alex Harvey" > To: "puppet-dev" > Sent: Sunday, 10 April, 2016 11:05:49 > Subject: Re: [Puppet-dev] Re: Idea: Deprecation logs > On 10 April 2016 at 03:59, R.I.Pienaar wrote: >> >> >> Not really sure

Re: [Puppet-dev] Re: Idea: Deprecation logs

On Sunday, April 10, 2016 at 3:59:21 AM UTC+10, R.I. Pienaar wrote: My apologies; I deleted my two posts; I am frustrated after losing the fight to Ansible after fighting for 2 years where I am. I don't mean to hijack this thread, support Rob's suggestion, and perhaps should write to someone

Re: [Puppet-dev] Re: Idea: Deprecation logs

> On 9 Apr 2016, at 11:34, Alex Harvey wrote: > > +1 > > The deprecation log is a great idea if we resign to the fact that Puppet Labs > (um, Puppet...) is never going to stop breaking things in its addiction to > change. Ansible & Salt - at least so far - are not inflicting this > particu

[Puppet-dev] Re: Idea: Deprecation logs

+1 The deprecation log is a great idea if we resign to the fact that Puppet Labs (um, Puppet...) is never going to stop breaking things in its addiction to change. Ansible & Salt - at least so far - are not inflicting this particular kind of pain on their users, and Puppet should charge ahead

[Puppet-dev] Re: Idea: Deprecation logs

Yes, it should probably break less. But change is eternal, so it's going to happen and its best we deal with it. It's not like this problem is relegated to only CM tools! If something like this happens with Puppet, it may end up being a good model to point other vendors to. On Sunday, March 20, 20

[Puppet-dev] Re: Idea: Deprecation logs

Hi Rob, nice proposal, would definitively help people to deal with the stated problem. Another approach could be to break and deprecate less things. Sure, I'm just kidding ;-) I love moving things forward. But you know, there's a grain of truth in every joke. We should not forget about the fact