On Nov 17, 2014, at 2:19 PM, Peter Meier wrote:
> And how will the release plan of PL looks like regarding 4.0? Will we
> end up with having 4.0 in the repositories one day and all the people
> that sync the repo (or directly update from it) will just update?
>
> Or will someone take over the d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Please note that some changes in puppet 4 mean that puppet 3
>> agents won’t be able to talk to puppet 4 masters (or vice-versa).
>> This probably means you don’t want to be updating puppet itself
>> with “ensure => latest” :)
>>
> point taken, but
On Mon, Nov 17, 2014 at 6:22 AM, Byron Miller wrote:
> I for one would love to feel more safe when tempting fate upgrading my
> puppet infrastructure. I like the idea of rolling upgrades (if upgraded,
> point here), but i would love to have some sort of process in puppet to
> handle this. A confi
I for one would love to feel more safe when tempting fate upgrading my
puppet infrastructure. I like the idea of rolling upgrades (if upgraded,
point here), but i would love to have some sort of process in puppet to
handle this. A configuration/feature flag that says "hey puppet, we're
upgradin
