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 |
|---|---|
|
|
October 29 |
|
|
December 15 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
March |
|
|
|
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 RFC2.1 - Moving Smart Proxy to SCL on RPM based systems RFC - done
- Upgrade PostgreSQL on RPM based systems RFC - done
- EL8 client repository support - done
- Katello with Pulp 3 support for File and Docker content types Roadmap - done
- Change default dynflow implementation to new sidekiq-based one RFC - done
- 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 - user facing part done, final cleanup will be in 2.1.
-
Rails 6 compatibility (or full support if we manage to finish the upgrade in time) Discussion- 2.1
- IPv6 initial provisioning and installer support (Ideas for IPv6 netboot provisioning) - basic installer support done, additional work in 2.1.
Refactoring of report storage for improved performance (RFC: Optimized reports storage)Incorporate apipie-dsl to document template macros. The documentation should be available as part of installed Foreman (similar to /apidoc).
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