Jira (PUP-1821) Bump facter dependency to 1.7 or greater

[Moses Mendoza (JIRA)]

Title: Message Title

Moses Mendoza commented on an issue   Re: Bump facter dependency to 1.7 or greater With the explicit understanding that facter 1.6 and 1.7 are fully backwards compatible, I'm ok with the dependency bump. In my interpretation of the Semver docs I think we're in accordance on this. Semver may actually reference this situation case explicitly in their docs: "A simple example will demonstrate how Semantic Versioning can make dependency hell a thing of the past. Consider a library called "Firetruck." It requires a Semantically Versioned package named "Ladder." At the time that Firetruck is created, Ladder is at version 3.1.0. Since Firetruck uses some functionality that was first introduced in 3.1.0, you can safely specify the Ladder dependency as greater than or equal to 3.1.0 but less than 4.0.0. Now, when Ladder version 3.1.1 and 3.2.0 become available, you can release them to your package management system and know that they will be compatible with existing dependent software. ... What should I do if I update my own dependencies without changing the public API? That would be considered compatible since it does not affect the public API. Software that explicitly depends on the same dependencies as your package should have their own dependency specifications and the author will notice any conflicts. Determining whether the change is a patch level or minor level modification depends on whether you updated your dependencies in order to fix a bug or introduce new functionality. I would usually expect additional code for the latter instance, in which case it's obviously a minor level increment."[1] +1 to the change. I will remark as much on the PR. My greatest concern is for users who rely on package systems without automatic dependency resolution (e.g., our Mac dmg packages). I'd like to call out explicitly in the release notes that users of OSX, etc will soon want to upgrade to facter 1.7 if they haven't already, as well as the potential issues they'll face if they cannot upgrade. [1] http://semver.org/ Add Comment   Puppet / PUP-1821 Bump facter dependency to 1.7 or greater Facter 1.7 has been out since April 2013 and we don't test against facter 1.6, so really can't make any guarantees about behavior with facter 1.6. In addition this is apparently a recurring issue for the modules team, where users manage to update puppet without ever updating facter. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.