Issue #16729 has been updated by Michael Arnold.
Jeff McCune wrote: > A.) What _value_ did Puppet Labs provide to the community by publishing > Puppet 3.0 in the same repository as 2.7? Ease of version upgrades via "yum update" (or apt-get). Nothing has to change on the customer end for this benefit. > Given that we know 3.0 is incompatible with 2.7; > B.) What _risk_ did Puppet Labs pass along to the community by publishing > Puppet 3.0 in the same repository as 2.7? "yum update" might result in a broken upgrade due to incompatibilities that may require manual intervention. My ability to decide to stay on 2.7 is removed as yum will pick the newest ENVR to update. Yes, I can use yum-versionlock, but then I am pinned to a precise version of the puppet RPM (ie 0:puppet-2.7.19-1.noarch) and will not see any new 2.7.x releases. Also, a newer version of ruby would have been installed on EL5 which could have caused breakage in third-party applications that depend on ruby 1.8.5. ---------------------------------------- Bug #16729: When using the puppetlabs repositories, `yum install puppet` should be safe. https://projects.puppetlabs.com/issues/16729#change-72721 Author: Robert Rothenberg Status: Unreviewed 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.
