Scope and Timeline for Puppet Platform 6.0.1

[Kenn Hussey]

Now that Puppet Platform 6.0.0 has been released (see here for details), I would like to draw your attention to the scope and timeline for the next release in the 6.0.z series, Puppet Platform 6.0.1.

Scope

The scope of this release includes fixes for problems with Puppet Platform 6.0.0 that are found by the community. Code for this release should land on the ‘6.0.x’ branch (and corresponding component branches) for puppet-agent, ‘6.0.x’ branch for PuppetDB, and ‘6.0.x’ branch for Puppet Server.

Timeline

The “String Freeze” milestone for this release is targeted for September 21. 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 September 25.

This means that all work for the release needs to be planned during the next week, with the goal of shipping the release on September 27.

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

Thanks,

--

Kenn Hussey

Program Manager

ke...@puppet.com | +1.613.301.9105

[Kenn Hussey]

FYI, the release of Puppet Platform 6.0.1 has been postponed to October 2 to increase the runway for potential "ship stopper" issues that may need to be fixed. 

On Tue, Sep 18, 2018 at 6:01 PM Kenn Hussey <ke...@puppet.com> wrote:

Now that Puppet Platform 6.0.0 has been released (see here for details), I would like to draw your attention to the scope and timeline for the next release in the 6.0.z series, Puppet Platform 6.0.1.

Scope

The scope of this release includes fixes for problems with Puppet Platform 6.0.0 that are found by the community. Code for this release should land on the ‘6.0.x’ branch (and corresponding component branches) for puppet-agent, ‘6.0.x’ branch for PuppetDB, and ‘6.0.x’ branch for Puppet Server.

Timeline

The “String Freeze” milestone for this release is targeted for September 21. 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 September 25.

This means that all work for the release needs to be planned during the next week, with the goal of shipping the release on October 2.

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

Thanks,