[Puppet-dev] Re: The Future of Puppet [Was: Deprecation logs]

Am 11.04.2016 um 03:01 schrieb Rob Nelson: > Of course there's lock in. You can't click a button and go from Puppet > OSS to Chef OSS; [...] > Is their concern about being able to contribute to it or even fork? I > suspect that's what most lock in concerns are really based on. It's about going f

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: The Future of Puppet [Was: Deprecation logs]

Lots of great discussion this weekend! I've changed the subject, since we've changed our subject and this may help with future searches on the ML archives. No doubt. I had above conversation with a customer who I convinced to by > PE the very same day. I explained it's advantages, they decided to

[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] Idea: Deprecation logs

On Apr 10, 2016, at 2:05 AM, Alex Harvey wrote: > I remember Nigel saying after Puppet 3 was released that Puppet would now > stabilise. That was in 2012, and yet here we are in 2016 and we have so many > deprecations coming that a dedicated deprecation log file to keep track of > them all se

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 I follow most of this rant. >> > > Yes, fair enough.

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