With 3.2.0 GA coming soon, it’s time to talk about the 3.3 timelines and schedule,
The 3.2 branched on February 10th, and to keep up our 3-month release cadence that would mean we should branch for 3.3 on May 10th.
- 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.
|3.3 Dev start||11th February||Friday|
|3.3 Half way point||28th March||Monday|
|3.3 Installer modules release week||25th to 29th April|
|3.3 Stabilization week||2nd to 6th May|
|3.3 Branching||10th May||Tuesday|
|3.3 RC1||12th May||Thursday|
|3.3 RC2||26th May||Thursday|
If you have a significant change that you wish to get into 3.3, 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.3, request to add which you are aware about,
Hammer 3.3 Katello 4.4 Discovery 21.0.1 Bootdisk 19.0.5 Puppet 4.0.0 Remote Execution Statistics 2.1? (or current 2.0) Tasks OpenSCAP 5.2.2 Ansible 7.2 Templates Leapp 0.1.10