Issue #16729 has been updated by Jeff McCune.
Jeff McCune wrote: > Finally, we acknowledge that using `ensure => latest` inside of Puppet, or > doing the equivalent of `yum install puppet` in kickstart, scripts, or > cobbler doesn't qualify as knowingly deciding to upgrade across incompatible > versions. Not everyone reads the documentation or our announcements, and not > everyone is an expert in apt and yum. This acknowledgement applies for any > system we support that has online repositories such as APT and IPS. > Furthermore, there is quite a bit of documentation [1] [2] [3] that indicates > this is a problem with our design. I'd like to amend the paragraph above because I prematurely spoke for Puppet Labs and more importantly our release engineering team who is responsible for our repositories. This paragraph is too prescriptive of the solution domain; the more general design principle we're subjecting ourselves to can be summed up as, "stupid users are a myth" and a good litmus test we are applying to this issue is; "If you're using our repositories, Puppet runs successfully 10 times in a row, and on the 11th run Puppet is broken," then that's a design issue we'll work to correct. ---------------------------------------- Bug #16729: When using the puppetlabs repositories, `yum install puppet` should be safe. https://projects.puppetlabs.com/issues/16729#change-73014 Author: Robert Rothenberg Status: Accepted Priority: High Assignee: Category: package Target version: Affected Puppet version: 3.0.0 Keywords: Branch: I work for a small company that is not yet ready to upgrade Puppet to v3. This upgrade may or may not cause problems for us (especially since we use a masterless network), but the upgrade will require us to devote time to test the upgrade. It would be much better if there were separate names for the distributions, say, puppet2. Users who want to delay upgrades can install puppet2 and use that until they are ready. # Updates JJM - I changed the title because different package names are a prescribed solution. There is at least one other alternative proposal, which is to use different repositories for incompatible releases. Whatever we decide on, yum install puppet should be safe for the end user. Releasing incompatible packages to the repository makes this unsafe for end users. # References * [Puppet Users - Puppet 2.7 v 3.0 in the PuppetLabs yum repo](https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/Q14kTSE0pvY) * [Puppet 3.0.0 Release Announcement](https://groups.google.com/d/topic/puppet-announce/lqmTBX9XDtw/discussion) * [Puppet 3.0.0 breaking changes relative to Puppet 2.7.x](http://links.puppetlabs.com/telly_breaking_changes) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
