Foreman 2.1 schedule and planning


With 2.0.0 coming soon, it’s time to talk about timelines and features for 2.1.

2.0 was branched last week, February 13th, and to keep up our 3-month release cadence that would mean we should branch for 2.1 on May 12th 2020.
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, I will ask your cooperation in focusing more on stabilizing and bug fixing and less on new features.

Proposed schedule for 2.1:

Event Date
2.1 Dev Start February 14
2.1 Half Way Point April 1
2.1 Stabilization May 4
2.1 Branch May 12 13
2.1 RC1 May 19
2.1 RC2 June 2 3
2.1 RC3 June 16 18
2.1.0 June 16 July 6

If you have a significant change that you wish to get into 2.1, please set the “Target Version” field on redmine at least for the main tracker for the bug. I will also ask maintainers to make sure that when merged, any major features are added to the “highlighted features” section on the manual, and any deprecations 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 major changes (please add more and update status as we progress):

In Progress:

  • EL8 installation support - targeting beta level support


Pushed to 2.2:

Lets also make a list of which versions of plugins and tools are planned to be compatible with 2.1, so that we know what to expect as well. Please add any that you are aware of below:

  • Katello 3.16
  • Hammer 2.1

Looks like I made a mistake (or was extremely optimistic…) when writing up the schedule and only had one week between RC1->2 and RC2->GA. Corrected the schedule to 2 weeks as usual.