Ah CFPropertyList, the gift that keeps on giving. With respect to CFPropertyList, we're still planning on pulling it out for Facter 2. Rubygems supports platform specific gems, so we can build a gem for OSX that has the CFPropertyList gem, and not add that dependency on other platforms. On the .pkg front we're going to bundle CFPropertyList in at package build time; it doesn't exist at this very moment but we're doing our best to move in that direction. In addition I'm under the impression that CFPropertyList was actually included in OSX 10.9, and if that's the case then we can just depend on the OS packages.
With respect to the contents of the next branch, we haven't decided what we're ultimately going to do with it. The goal is to get Facter master into a releasable state now, and in the medium - long term incrementally transfer and release the work accumulated in next. We're not bound to just backporting patches to 2.0.0 and 2.1.0, as long as a given patch is backwards compatible we can merge it in the 2.x line. With respect to backwards incompatible patches we will have to wait till Facter 3 or enable those features with feature flags, but there's nothing preventing us from releasing that somewhat soon. With luck we'll hit the point where we've managed to move all the behavior from next into master and we can delete the branch. However, we have to kickstart things in some manner and if it's between delaying the release of patches in master and waiting another year or so to release Facter 2, I would prefer the former. On Tue, Dec 3, 2013 at 2:49 PM, Dustin J. Mitchell <[email protected]>wrote: > I understand the rename of master -> next and stable -> master, and > the backporting of some features from next, but what's to become of > next in general? If a patch in that branch doesn't come to someone's > attention in 2.0.0 or 2.1.0, will it ever make it into a release? > > I'm not terribly invested in the answer to this question, aside from > (I assume) blocking the decision on CFPropertyList, but the answer > isn't clear from your note. > > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/CAJtE5vS6R%3D6BnW5%3D-3YB%3D%3D2pPr2ho21_4kuLoOUoWR66zwNT1g%40mail.gmail.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- Adrien Thebo | Puppet Labs -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CALVJ9SLN1igu2Sh1chNQFC47h-r4QvsgcaJTPzfNqDeOubAb9A%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
