Foreman 3.1 Schedule and Planning


With 3.0.0 GA coming soon, it’s time to talk about the 3.1 timelines and schedule,

The 3.0 branched on August 6th(delayed by few days), and to keep up our 3-month release cadence that would mean we should branch for 3.1 on November 2nd.

As before, we will be doing a stabilization week prior to branching to ensure we have working nightlies when branching. Larger changes should be merged as early as possible in the release cycle, to ensure enough time to fix bugs prior to branching. Keep in mind that installer module changes should also be merged prior to the stabilization week. As we near the branching date, we shall ask your cooperation in focusing more on stabilizing and bug fixing and less on new features.

Event Date
3.1 Dev start August 4th
3.1 Half way point September 17th
3.1 Installer modules releases October 18th to October 22nd
3.1 Stabilization week October 25th to October 29th
3.1 Branching November 2nd 9th 11th
3.1 RC1 November 4th 11th 15th
3.1 RC2 November 18th 29th
3.1.0(GA) December 2nd 8th

If you have a significant change that you wish to get into 3.1, request to set the “Target Version” field on redmine at least for the main tracker for the bug. We also request maintainers to make sure that when merged, any major features are added to the “highlighted features” section on the manual, and any deprecation or changes in behavior are also added to the relevant sections. If you wish to discuss any plans, this post’s comments can and should be used for that.

Planned changes are being tracked in redmine as roadmap. Have a look if you wish to contribute or keep track of something important.

The versions of plugins and tools which are planned to be compatible with Foreman 3.1, request to add which you are aware about,

Katello 4.3
Hammer 3.1
Discovery 19.0
Bootdisk 19.0
Puppet 2.0
Remote Execution 5.0
Statistics 2.0
Tasks 5.2
OpenSCAP 5.1
Ansible 7.0
Templates 9.1
Leapp 0.1.7