Hot on the heels of Puppet 3.5 comes Puppet 3.6.0. We said things were going to 
accelerate in Puppet's open-source release cadence, and here it is.

Puppet 3.6.0 is a backward-compatible features and fixes release in the Puppet 
3 series. The biggest things in this release are:

        * Improvements to directory environments, and the deprecation of config 
file environments
        * Support for purging unmanaged ssh_authorized_key resources
        * Support for installing gems for a custom provider as part of a Puppet 
run
        * A configurable global logging level
        * A configurable hashing algorithm (for FIPS compliance and other 
purposes)
        * Improvements to the experimental future parser

Notable community contributions in this release include Felix Franks' great 
work on the ssh authorized keys type, fixing a feature request from 2008, and 
Jared Jennings for dilligently working through some epic pull request threads 
to add FIPS compliance.

Please read through the Release Notes for the full list of changes: 
http://docs.puppetlabs.com/puppet/latest/reference/release_notes.html
To install Puppet, follow the Installation Guide: 
http://docs.puppetlabs.com/guides/install_puppet/pre_install.html
To report issues with the release, file a ticket in the "PUP" project on 
https://tickets.puppetlabs.com/ and set the "Affects version/s" field to 
"3.6.0".
To see a list of known issues slated for the next bugfix release, follow this 
JIRA query: https://tickets.puppetlabs.com/issues/?filter=12246

Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles

-- 
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/4DBEF226-21BB-4F72-9160-E03BB6B85103%40puppetlabs.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to