On 2014-08-28 00:51, Kylo Ginsberg wrote:
But going forward there's a question about how to handle changes to fact
*values*. One proposal is that we identify (and of course test against)
some essential facts that we "care a lot about" (such as
'lsbmajdistrelease") and set some rules, like:
(a) we do not change those in x.y.Z releases
(b) we highlight it when they DO change in x.Y or X releases
Strict semver would suggest that (major) changes to values be marked
with an increment in the major version.
If it is properly documented though, manifests can conditionalize any
changes on $::facterversion. Annoying, but doable if properly documented.
Regards, David
--
* Always looking for people I can help with awesome projects *
G+: https://plus.google.com/+DavidSchmitt
Blog: http://club.black.co.at/log/
LinkedIn: http://at.linkedin.com/in/davidschmitt
--
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 puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/53FEFD2C.9020603%40dasz.at.
For more options, visit https://groups.google.com/d/optout.
