On Mon, Nov 5, 2012 at 7:10 PM, Tim Sharpe <[email protected]> wrote:
> I would consider stripping whitespace to be a bugfix rather than a > backwards incompatible change. > > Unfortunately a lot of bugfixes end up being backwards incompatible. One that I'm on the fence about for 1.7.0 is the fix for #14827. It is a bugfix, looks innocuous and provides a nice consistency across platforms. BUT it is a breaking change if anyone depended on those values. > On 03/11/2012, at 7:47 AM, Andy Parker <[email protected]> wrote: > > Right now facter has a branch called 2.x, which was supposed to be getting > ready for a 2.0.0 release of facter. That hasn't happened yet and there are > quite a few changes on the 2.x branch (and master since there are no > differences between the two). I'd really like to see those changes be > released and after looking over them I think we should release most, but > not all, of those changes as a Facter 1.7.0. > > In my analysis of the changes between the 1.6.x branch and the 2.x branch > I found: > * external facts (new feature, backwards compatible) > * whitespace stripping (new feature, backwards incompatible) > * various new facts (backwards compatible) > * removal of the memorytotal fact (backwards incompatible) > * removal of the iphostnumber fact (backwards incompatible) > * changes to the memory facts (backwards incompatible) > > So the plan would be to make a 1.7.x branch off of master and revert those > backwards incompatible changes. Remove the 2.x branch and have development > toward Facter 2 take place on master. > > However, even with that, there would need to be some QA and testing love > given to the 1.7.x branch. I can make the branch and revert the obviously > problematic changes, but I'd really like some help on trying it out and > getting it in shape for a release. Other ways people could help out would > be to work out a way of making some of those changes not be backwards > incompatible (for instance the changes to the memory facts could probably > be fixed up). > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" 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-dev?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" 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-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
