Issue #16729 has been updated by Jeff McCune.
R.I. Pienaar wrote: > -1, package managers support version pinning. If your goal is repeatable > builds or to rely on some old version of software then you should fix that in > your build/management process. This may be true, however, if we know our actions are going to cause (potentially serious) problems for a subset of our users, then it is certainly worth investigating the possibility of changing our own behavior. Please do not take this down-vote to mean we will not investigate or consider alternative Puppet release strategies, and please upvote if you were negatively affected even if you are not using version pinning. -Jeff ---------------------------------------- Bug #16729: Puppet v3 and Puppet v2.7 should have different names for distributions on the PuppetLabs repo https://projects.puppetlabs.com/issues/16729#change-72377 Author: Robert Rothenberg Status: Unreviewed Priority: High Assignee: Category: Target version: Affected Puppet version: 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. -- 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.
