-----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 what will the update plan look like for a large > installation? Will users be required to incorporate MCollective or > similar to be able to upgrade their agents?
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 duty and run around with a red flag the weeks before the release, as it is going to be problem? (Henrik actually just started that... ;-) ) How does actually the time schedule for 4.0 look like? Currently, the project says beginning of January: https://tickets.puppetlabs.com/browse/PUP/ 2015/01/07 Just to be able to be aware of breaking changes and one might actually monitor their repos more closely. ~pete -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlRqdFcACgkQbwltcAfKi392RACgkAZoRpJB2NXRbkjBPPWwz4ho oQ0AnjypKItk6GUDKvYmyN9dy9q9v/Pr =P0yE -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/546A7465.6080301%40immerda.ch. For more options, visit https://groups.google.com/d/optout.
