** Next PR Triage Wednesday, November 19th @ 10:00 am Pacific. ** Priorities
Commentary Puppet: We are going to keep 3.7.4 in parallel with 4.0.0 to ensure we get a 3x release that contains a future parser that is as close as possible to what is released in 4.0.0. It will be released in close proximity to 4.0.0 (unless there is a burning need to release it sooner). Please note that some changes in puppet 4 mean that puppet 3 agents won’t be able to talk to puppet 4 masters (or vice-versa). This probably means you don’t want to be updating puppet itself with “ensure => latest” :) One of these changes is for the URL structure for the master/agent HTTP API. Specifically, we’d like to move the environment name away from being the first segment of the URL, so that the URL space is more well-contained and predictable. This will allow us to begin separating the monolithic “master” service into more fine-grained services. Code removals for puppet 4 is picking up more steam (yay, burn all the things…) - 17k lines removed so far. See a heads up below if you are doing advanced things with any of the classes under puppet/parser (an additional 15k removal). We are doing major triage for 4.0.0 as we have accumulated quite a bit of scope creep. You will be seeing tickets move to target 4x as we like to reserve the 4.0.0 tag for things that we feel are required for this release. This means that we may pull in tickets/PRs marked 4x, but we will not block the release if they do not make it in time. We are also engaged in yet more work around environments - this time removing support for legacy environments. Puppet Server: Puppet Server 0.4.0 was released! The changes were mostly plumbing; packaging improvements, tweaks to make the CA behavior more consistent with the old CA, and some improvements related to SSL transports. We’re planning for the next release to be our 1.0 release. It will include a few cool new features related to directory environment caching, plus a few minor tweaks and bug fixes. The 1.0 series will be compatible with the Puppet 3.7.x, so next up will be to start working on Puppet Server 2.0 for Puppet 4.x compatibility.
Puppet Doc: We have worked on the scope of the new puppet doc implementation (puppet strings), there are now tickets, and we are just starting to work on those. Native Facter: Solaris, Windows, ec2/gce facts are all in - there are a handful of misc fix-it tickets remaining before we tag 0.3.0. Also, we now have Native Facter nightlies! Right now it’s rhel6/rhel7/wheezy with more packages coming. Try it out and tell us what we’re missing :) Other conversations of note:
Heads up on Code Removals With the fix in PUP-2906 being merged (reimplementation of collections) we now freed up for the removal of the old AST classes and work is now ongoing on ticket PUP-3274, which removes the AST and switches puppet 4.0.0 over to always using the future parser. As a heads up (if you have written code that relies on any of the parser classes), this means that:
Remaining AST:
ALL OTHER AST CLASSES HAVE BEEN REMOVED. If you have logic that makes use of those you need to do things differently. Please ping if you are in this situation and need help with the transition. Regards Henrik Lindberg henrik.lindb...@puppetlabs.com -- Visit my Blog "Puppet on the Edge" http://puppet-on-the-edge.blogspot.se/ -- |
- [Puppet-dev] puppet-dev status the week ending 14-11-14 Henrik Lindberg
- [Puppet-dev] Re: puppet-dev status the week ending 14... Henrik Lindberg
- [Puppet-dev] Re: puppet-dev status the week ending 14... Henrik Lindberg
- Re: [Puppet-dev] Re: puppet-dev status the week e... Felix Frank
- Re: [Puppet-dev] Re: puppet-dev status the we... Erik Dalén
- Re: [Puppet-dev] Re: puppet-dev status th... Chris Price
- Re: [Puppet-dev] Re: puppet-dev status the we... Byron Miller
- Re: [Puppet-dev] Re: puppet-dev status th... Chris Price
- Re: [Puppet-dev] Re: puppet-dev status the we... Peter Meier
- Re: [Puppet-dev] Re: puppet-dev status th... Eric Sorenson
- [Puppet-dev] Re: puppet-dev status the week ending 14... Mike Hendon