Issue #16729 has been updated by R.I. Pienaar.
Jeff McCune wrote: > I think we're missing the point on these key questions: > > Given that we know 3.0 is incompatible with 2.7; > > A.) What _value_ did Puppet Labs provide to the community by publishing > Puppet 3.0 in the same repository as 2.7? we made our software available on a more rapid schedule than those in the more reliable and conservative locations like EPEL. I dont think that question is of making the two available in the same repo is relevant unless you're just specifically trying to phrase a question in a way that leads the answer. > > B.) What _risk_ did Puppet Labs pass along to the community by publishing > Puppet 3.0 in the same repository as 2.7? None, the repository is a source for the current and past releases of puppet. Users have to decide if using a repository that provides the current version of Puppet suits their business and operational needs. > Does the value we're providing to our users significantly outweigh the risk > we're passing along? If so, then we did fine and should keep doing it, if > not, then we have a pretty clear indicator that replacing Puppet 2.7 with 3.0 > was a mistake because the reward doesn't justify the risk. Having a reliable source to find the current and even development releases for early adopters is very valuable, it's exactly what this repository is vs the more conservative sources like EPEL, Debian official, Ubuntu official etc. It is used by people who feel those sources lag behind too much. If someone needs a reliable repository that only maintains well trusted and proven branches their operatinsystem almost certainly provides this. What we did not do is document our policies. It could be that there is value in providing a EPEL like releases-we-consider-to-be-the-stable-version repository but I don't believe that is the goal of the current repositories and do I do not think the current repositories should change. If we feel a 'production' release repository is important and has use then we should create a new repository with that behaviour. Some might say that's what PE is. ---------------------------------------- Bug #16729: When using the puppetlabs repositories, `yum install puppet` should be safe. https://projects.puppetlabs.com/issues/16729#change-72544 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.
