With 3.5 GA behind us, I should have posted this a while back already. Foreman 3.5 branched on 2022-11-09, so 3 months after that means 3.6 branching is 2023-02-08. This is actually during Config Management Camp and the people who usually perform it are present at the conference (and doing talks). Post-conference days are usually not the best, so to be safe we’ll branch the week after on Tuesday 2023-02-14. I’m sure everyone will love that valentine’s gift. Additionally, like with Foreman 3.5 we’ll aim at RC1 on the same day as branching.
- As before, we will be doing a stabilization week prior to branching to ensure we have working nightlies when branching. This should also be the considered the string freeze period, to give translators sufficient time.
- 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.6 Dev start||2022-11-09||Thursday|
|3.6 Half way point||2022-12-23||Friday|
|3.6 Installer modules release week||2023-01-30 - 2023-02-06|
|3.6 Stabilization week||2023-02-06 - 2023-02-10|
If you have a significant change that you wish to get into 3.6, 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 (Foreman and Katello). If you wish to discuss any plans, this post’s comments can and should be used for that.
The versions of plugins and tools which are planned to be compatible with Foreman 3.6, request to add which you are aware about. Below are all Foreman plugins supported by the installer.