We're pleased to announce that Puppet Server 1.0.8 is now available.

This release is a bug fix / maintenance release in the Puppet Server 1.x 
series. In accordance with the Semantic Versioning <http://semver.org> 
specification, 
this release contains fixes for bugs reported against the 1.0.2 release.

Puppet Server versions 1.0.3 through 1.0.7 were not released, hence the 
move from 1.0.2 to 1.0.8.

In addition, the following issues have been resolved:

* (SERVER-448) Change default max-active-instances to not exceed 4 JRubies
* (SERVER-379) Tuning guide for JRubies, Heap size, etc.
* (SERVER-380/513) Upgrade Jetty to 9.2.10 and changes to 
shutdown-timeout-seconds and max-threads defaults
* (SERVER-273) Upgrade to JRuby 1.7.19 / fix for jruby-pool DELETE memory 
leak
* (SERVER-319) Enable apache-style http access logs by default
* (SERVER-336/404) Properly create /var/run/puppetserver dir at service 
startup
* (SERVER-356) puppetserver foreground produces no output
* (SERVER-344) Startup scripts should use 'runuser' not 'su'
* (SERVER-345) Fixup usages of cacert / localcacert in master
* (SERVER-449) Exposed http-client timeouts from Puppet Server
* (SERVER-408) Expose configurable `borrow-timeout` to allow JRuby pool 
borrows to timeout
* (SERVER-517) Re-raise HttpClientException as Ruby SocketError from 
http-client handler

See the complete release notes for details about these changes:
https://docs.puppetlabs.com/puppetserver/1.0/release_notes.html

For a list of all changes in this release, check out the JIRA page:
https://tickets.puppetlabs.com/browse/SERVER/fixforversion/12807

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/21183f9c-4ed4-4140-a428-e8748106e6bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to