As specified in our timed-release cycle process, we've entered the
THUNDERDOME for the 2.7.15 series (May) vs 2.7.16 series (June).

Two releases enter; one leaves.

It was determined today that 2.7.16 has won the Thunderdome.  (An epic
battle, 2.7.15 put up a good fight and looked like it would knock
2.7.16 out until 2.7.16 used some new SSL abilities to distract 2.7.15
and push it over a cliff.)

So, look for 2.7.16rc1 later today.

The main reason for holding back 2.7.15 were concerns around SSL
compatibility between Ruby 1.8 and Ruby 1.9.

1.  Ruby 1.8 defaults to an SSL verify_mode of NO_VERIFY while Ruby
1.9 defaults to PEER_VERIFY. This is addressed by specifying which is
desired and not using Ruby's default value.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to