Foreman <strike>1.25</strike> 2.0 schedule and planning

Hello,

With 1.24.0 coming soon, it’s time to talk about timelines and features for 1.25 2.0.

1.24 was branched yesterday, October 29th, and to keep up our 3-month release cadence that would mean we should branch for 1.25 2.0 on January 27th 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. Keep in mind that during this cycle many people will be away for holidays in late December and plan accordingly.

Proposed schedule for 1.25 2.0:

Event Date
1.25 2.0 Dev Start October 29
1.25 2.0 Half Way Point December 15
1.25 2.0 Stabilization January 20 February 3
1.25 2.0 Branch January 27 February 10
1.25 2.0 RC1 January 31 February 14
1.25 2.0 RC2 February 14 26
1.25 2.0.0 February 28 March 11

If you have a significant change that you wish to get into 1.25 2.0, 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:

  • Foreman default deployment to Puma with an Apache reverse proxy RFC 2.1
  • Moving Smart Proxy to SCL on RPM based systems RFC
  • Upgrade PostgreSQL on RPM based systems RFC
  • EL8 client repository support
  • Katello with Pulp 3 support for File and Docker content types Roadmap - at risk
  • Change default dynflow implementation to new sidekiq-based one RFC
  • Drop support for Ubuntu Xenial - done
  • Drop support for Debian Stretch - done
  • Drop support for MySQL RFC - done
  • Drop support for SQLite in production RFC - done
  • Drop support for Smart Variables in Puppet Classes RFC
  • Rails 6 compatibility (or full support if we manage to finish the upgrade in time) Discussion - 2.1

I would like to get a list of which versions of plugins and tools are planned to be compatible with 1.25 2.0, so that we know what to expect as well. Please add any that you are aware of below:

  • Katello 3.15
  • Hammer 0.20

Here is an initial list of changes that I am aware of being planned:

  • Foreman default deployment to Puma with an Apache reverse proxy
  • Moving Smart Proxy to SCL on RPM based systems
  • Upgrade PostgreSQL on RPM based systems
  • EL8 client repository support
  • Katello with Pulp 3 support for File and Docker content types
1 Like

Thanks! added a list of planned changes in the main post above which is a wiki so other may add more as well.

I added some RFC links, but ideally we’d have some design for changes. In cases like dropping Xenial or adding EL8 client repo support it’s probably not that relevant because it’s barely any real change.

1 Like

we have postponed branching by two weeks per Release meeting 2020-01-15, the schedule and list of features has been updated above.