Issue #16729 has been updated by Robert Rothenberg.

Jeff McCune wrote:
 
> 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.

The effects of the way Puppet 3.0 has been published are that people who used 
the repo for their deployments have to put in a lot of work to prevent Puppet 
from upgrading (either creating their own repos, or various workarounds to keep 
tell yum as well as deployment systems such as Cobbler not to upgrade the 
module).

A very simple and quick fix would be to create an alias package such as 
"puppet2.7" or "puppet3", so that users of the repo can adjust the the name of 
the package that they use.

----------------------------------------
Bug #16729: When using the puppetlabs repositories, `yum install puppet` should 
be safe.
https://projects.puppetlabs.com/issues/16729#change-72539

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.

Reply via email to