On Sat 18 Apr 2015 at 22:36, Jonathan Steel wrote: > Hi, > > Puppet 4 has been released and will require manual intervention. I'll push > a package to [community-testing] soon, but I think this is worthy of a news > announcement before hitting [community]. I'm in two minds about keeping a > puppet3 package around, some users may want to stick with that for now; I > would be interested to hear some opinions. > > Puppet 4 has been released and breaks compatibility with version 3. > Therefore users will need to upgrade a server to Puppet 4 before updating > their clients. Note that if only a Puppet 4 server is available, Puppet 3 > clients will not work. Also a number of locations for things have changed > including the config, manifest and module files. You will need to follow > upgrade instructions for your servers and clients: > > https://docs.puppetlabs.com/puppet/4.0/reference/upgrade_server.html > https://docs.puppetlabs.com/puppet/4.0/reference/upgrade_agent.html > > [...]
Hi, puppet-4.0.0-2 has been in [community-testing] for three weeks without any complaints so I would like to move it to [community], to replace puppet 3. Could someone post (or comment on) the news announcement? Thanks, -- Jonathan Steel
pgpNMJ7CvcXSB.pgp
Description: PGP signature
