Decide exactly what versions of Ruby we support
|Affected Puppet version:||Branch:|
|Keywords:||puppet ruby version support|
There has been a lot of talk about this, but so far the decision either hasn’t been made, or hasn’t been documented and communicated clearly. The impression I got from the testing meeting was that we only support Ruby 1.8.5 and 1.8.7 with a commitment to support 1.9.2 in 2.7.x. However, our public facing documentation states we support any version of Ruby 1.8.1 and above http://docs.puppetlabs.com/guides/platforms.html. Our README file also states this https://github.com/puppetlabs/puppet/blob/master/README.md
We need to either update the Docs site and README to clarify our ruby version support, or test more versions of Ruby.
#2 Updated by Matt Robinson over 2 years ago
I talked to Nigel and Jason and Jacob and Daniel and Dominic and probably others about this, and it’s determined that we should change our documentation to be clearer about the versions of Ruby we support. Jason and Nigel will do the wordsmithing, but basically we’ll test against Ruby 1.8.5 and 1.8.7 for Puppet 2.6, and add Ruby 1.9.2 for Puppet 2.7. Once they’ve worded it how they’re happy, anyone should be able to update the appropriate places.
#4 Updated by Jason McKerr over 2 years ago
We support and test against Ruby 1.8.5 and 1.8.7 for all Puppet versions up to and including 2.6.x.
We make best effort support for Ruby 1.8.1, but do not execute our automated tests against that Ruby version.
For Puppet 2.7.x we wil support and test against Ruby 1.9.2 in addition to 1.8.5 and 1.8.7.
We do not support Ruby 1.8.6 and 1.9.0 and 1.9.1 because those versions are not included in major platform/OS distributions and they have compatibility issues with other versions of Ruby.
#7 Updated by Matt Robinson over 2 years ago
- Status changed from Re-opened to Merged - Pending Release
- Assignee deleted (
NickF and I paired on this to update both 2.7rc commit:1a33bf86b74053f7978bddb6b1f715d04db9f2ba and 2.6.x commit:db1a392e3fce0d616b6d1061a123b60f61470f20. Nick is also updating the FAQ on the docs site.