On Mon, 2013-09-02 at 23:50 -0700, Luke Kanies wrote: > However, I still disagree that fixing bugs should constitute a change > worth upping a major rev. If it's a bug, then fixing it shouldn't be > an incompatibility, should it?
I would argue that it has been the behavior for so long that fixing it now could possibly break things in production and, at this point, it's more or less past "a bug" and into a new feature. I'm sure there are lots of users of Puppet at this point who have never known another behavior. I use the anchor pattern extensively, but I seem to recall places where I explicitly did not use it in some modules. At the moment, I don't recall if that was because I didn't care if it was contained or if it was because I definitely did not want it to be contained, but I feel like "fixing" this would potentially break some of my current modules. And, to be clear, I'm NOT saying don't fix it, but unless you can be certain it won't break things out in the wild save it until an expected backwards incompatible version break (i.e.: Puppet 4) Sean -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
