Scope and Timeline for Puppet Platform 5.5.2

79 views
Skip to first unread message

Kenn Hussey

unread,
Apr 20, 2018, 9:41:03 AM4/20/18
to puppe...@googlegroups.com
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.

Scope

The 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 July 6. 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 July 11.

This means that all work for the release needs to be planned during the next three weeks, with the goal of shipping the release on July 17.


If you have any questions or concerns about any of this, please let me know.

Thanks,

--
Kenn Hussey
Program Manager, Puppet Platform

Kenn Hussey

unread,
May 9, 2018, 4:45:29 PM5/9/18
to puppe...@googlegroups.com
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.

Scope

The 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,

Kenn Hussey

unread,
May 24, 2018, 3:41:40 PM5/24/18
to puppe...@googlegroups.com
We encountered issues while testing that will require us to ship this release later than originally planned. Our new target date is May 31, also reflected below.

On Wed, May 9, 2018 at 4:45 PM, Kenn Hussey <ke...@puppet.com> wrote:
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.

Scope

The 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 31.


If you have any questions or concerns about any of this, please let me know.

Thanks,

Kenn Hussey

unread,
May 30, 2018, 8:37:46 PM5/30/18
to puppe...@googlegroups.com
Unfortunately we have uncovered additional issues which require us to postpone this release again. I will follow up with a new target date as soon as one is available.

Kenn Hussey

unread,
Jun 7, 2018, 12:46:55 PM6/7/18
to puppe...@googlegroups.com
Apologies for the delayed update, but we'll be shipping this release today, June 7.
Kenn Hussey
Program Manager

Reply all
Reply to author
Forward
0 new messages