An update on what I found. Also once we put out 1.7.0, the 1.6 line will be in a "major bugfix only" mode since. There is also the question of what we should do with the 2.x branch. My current inclination is to drop it, and start following the development and branching model that we have on puppet now: 1.6.x is very rarely updated and only for major problems (probably security fixes), 1.7.x is updated with specific bug fixes, master is forward looking development. Depending on the features that are going to go into master it could either be a 1.8.x cut from it next or a 2.0.x.
More information inline On Fri, Nov 2, 2012 at 1:47 PM, 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) > Kept this > * whitespace stripping (new feature, backwards incompatible) > Reverted this > * various new facts (backwards compatible) > Kept these > * removal of the memorytotal fact (backwards incompatible) > Reverted this > * removal of the iphostnumber fact (backwards incompatible) > Reverted this > * changes to the memory facts (backwards incompatible) > Kept this. It turned out to only be a bug fix for #14827, only affected a single swap size fact on OSX and made that fact consistent with other memory facts. This is technically backwards incompatible, but I think it would be a good one to have. I'm willing to be talked out of it, though. > > 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. > I haven't deleted the 2.x branch yet. There are a couple pull requests open against it (don't have the numbers available), and deleting the branch will close those. I'd like to at least put a comment on them about what is happening before they close. > > 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.
