Update CHANGELOG, Modulefile for 2.1.3
(#13494) Specify the behavior of zero padded strings

Without this patch the specified behavior of strings that are numeric
only and zero padded is unclear and untested in the spec tests.  This is
a problem because it's not clear that range('00', '10') will actually
return [ "0", "1", ..., "10" ] instead of [ "00", "01", ..., "10" ]

This patch addresses the issue by providing explicit test coverage.  If
the string conversion behavior of puppet changes, this test will begin
to fail.
Merge branch 'maint/2.2.x/range_spec_tests' into 2.2.x

* maint/2.2.x/range_spec_tests:
  (#13494) Specify the behavior of zero padded strings
Merge branch '2.1.x' into 2.2.x

* 2.1.x:
  Update CHANGELOG, Modulefile for 2.1.3

Conflicts:
	CHANGELOG
	Modulefile
Merge branch '2.2.x' into 2.3.x

* 2.2.x:
  (#13494) Specify the behavior of zero padded strings
  Update CHANGELOG, Modulefile for 2.1.3

Conflicts:
	CHANGELOG
	Modulefile
Merge branch '2.3.x'

* 2.3.x:
  (#13494) Specify the behavior of zero padded strings
  Update CHANGELOG, Modulefile for 2.1.3
Merge pull request #53 from traylenator/fqdn_rotate

(#13205) Rotate array/string randomley based on fqdn, fqdn_rotate()
(#13439) refactor spec helper for compatibility with both puppet 2.7 and
master
Merge branch 'ticket/2.2.x/13439_fix_spec_helper' into 2.2.x

* ticket/2.2.x/13439_fix_spec_helper:
  (#13439) refactor spec helper for compatibility with both puppet 2.7 and master
Merge branch '2.2.x' into 2.3.x

* 2.2.x:
  (#13439) refactor spec helper for compatibility with both puppet 2.7 and master
(#13439) Fix test failures with Puppet 2.6.x

Without this patch the spec_helper sends a message named
initialize_everything_for_tests to Puppet.settings.  This is a problem
because Puppet 2.6.x does not have this method, only Puppet 2.7.x and
Puppet master have this method at this time and we're getting false
positive test failures.

This patch fixes the problem by looking before we leap.  We test if the
private method exists before calling it.  This works with Ruby 1.8.5 and
onwards and Puppet 2.6, 2.7 and master.

This should fix all of the failures I've caused in Jenkins today.
Merge branch 'ticket/2.2.x/13439_fix_spec_helper_try2' into 2.2.x

* ticket/2.2.x/13439_fix_spec_helper_try2:
  (#13439) Fix test failures with Puppet 2.6.x
Merge branch '2.2.x' into 2.3.x

* 2.2.x:
  (#13439) Fix test failures with Puppet 2.6.x
Merge branch '2.3.x' into 2.4.x

* 2.3.x:
  (#13439) Fix test failures with Puppet 2.6.x
  (#13439) refactor spec helper for compatibility with both puppet 2.7 and master
Merge branch '2.4.x'

* 2.4.x:
  (#13439) Fix test failures with Puppet 2.6.x
  (#13439) refactor spec helper for compatibility with both puppet 2.7 and master
(#13439) Fix MRI 1.9 issue with spec_helper

When using MRI 1.9.x the stdlib spec helper does not invoke because
Puppet.settings.private_methods returns symbols instead of strings.

This is a problem because we need to set default configuration settings
like Puppet[:vardir] when using the compiler.

This patch fixes the issue by simply checking the Puppet version.  This
seems a better choice than rescuing NoMethodError since the method might
be renamed or removed in the future.
Merge branch 'ticket/2.2.x/13439_fix_spec_helper_try3' into 2.2.x

* ticket/2.2.x/13439_fix_spec_helper_try3:
  (#13439) Fix MRI 1.9 issue with spec_helper
Merge branch '2.2.x' into 2.3.x

* 2.2.x:
  (#13439) Fix MRI 1.9 issue with spec_helper
Merge branch '2.3.x' into 2.4.x

* 2.3.x:
  (#13439) Fix MRI 1.9 issue with spec_helper
Merge branch '2.4.x'

* 2.4.x:
  (#13439) Fix MRI 1.9 issue with spec_helper