Now that Puppet Platform 5.5.1 has shipped, I would like to draw your attention to the scope and timeline for the next release in the 5.5.z series, Puppet Platform 5.5.2.ScopeThe scope of this release includes fixes for security vulnerabilities and problems with Puppet Platform 5.5.1 that are found by the community. Code for this release should land on the ‘5.5.x’ branch (and corresponding component branches) for puppet-agent, ‘5.2.x’ branch for PuppetDB, and ‘5.3.x’ branch for Puppet Server.Timeline
The “String Freeze” milestone for this release is targeted for May 16. This is the date by which all changes affecting translatable strings must be complete (so that we have time to request, obtain, and merge translations before we ship).The “Stop Ship Line” milestone, by which time all planned code changes must be complete, is targeted for May 21.This means that all work for the release needs to be planned during the next two weeks, with the goal of shipping the release on May 30.
If you have any questions or concerns about any of this, please let me know.Thanks,
We have decided to ship this release earlier than originally planned in order to get some critical fixes into an official release sooner. See below for updated target milestone dates.
On Fri, Apr 20, 2018 at 9:41 AM, Kenn Hussey <ke...@puppet.com> wrote:
Now that Puppet Platform 5.5.1 has shipped, I would like to draw your attention to the scope and timeline for the next release in the 5.5.z series, Puppet Platform 5.5.2.ScopeThe scope of this release includes fixes for security vulnerabilities and problems with Puppet Platform 5.5.1 that are found by the community. Code for this release should land on the ‘5.5.x’ branch (and corresponding component branches) for puppet-agent, ‘5.2.x’ branch for PuppetDB, and ‘5.3.x’ branch for Puppet Server.TimelineThe “String Freeze” milestone for this release is targeted for May 16. This is the date by which all changes affecting translatable strings must be complete (so that we have time to request, obtain, and merge translations before we ship).The “Stop Ship Line” milestone, by which time all planned code changes must be complete, is targeted for May 21.
This means that all work for the release needs to be planned during the next two weeks, with the goal of shipping the release on May 31.
If you have any questions or concerns about any of this, please let me know.Thanks,