On Sun, Sep 1, 2013 at 9:52 AM, Dustin J. Mitchell <[email protected]>wrote:
> The switch to semantic versioning has been pretty broadly announced > and discussed. It will benefit from being seen in action, and from a > smooth start. Which means sooner rather than later, and fewer > compatibility breakages rather than more. It's easier for users to > work off a short list of "BREAKING CHANGES" in release notes than a > long list, even if that means dealing with breaking changes more > often. > > So I'd suggest moving on to 4 even if there are no huge breaking > changes. Find a few (OTOMH, requiring '@' in erb would be one) > breaking changes, add some deprecations targeted at puppet 5, write it > all up clearly, and ship it. Users will get practice upgrading major > versions and early warning (via deprecation) of changes in puppet 5. > > Also, I think we've all got features or fixes we'd love to see, but I > don't think this thread is the place to advocate putting work *into* a > release; rather, it's a place to decide in which version which > in-progress changes will land. > > I think I agree completely. I'm starting to think that the decision for a Puppet 4 shouldn't be about "we want to make some changes that cause breaks", but instead "we want to remove some cruft and switch the default on a few feature flags". Given that, then we already have a few breaks that we can do based on feature flags (hyphens in names is the one that I can think of) and a bunch of cruft that we can remove (all of the deprecated code). It seems like those would add up to small breaks, but would still be useful to do since a lot of the deprecated things are parts of the system that we just don't want to have around anymore (active record store configs, puppet queue, insecure yaml, insecure variable access in templates). > Dustin > > -- > 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. > -- Andrew Parker [email protected] Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at PuppetConf 2014, September 23-24 in San Francisco* -- 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.
