With 1.19 branched, it’s time to start looking at the 1.20 schedule and roadmap.
1.20 branching will be October 16th, 3 months from the 1.19 branching. Refraining from merging significant changes in the days leading up to the release seems to have had a positive impact and I would like to continue with this and perhaps even improve on it.
One idea that has been brought up is to try and do a test week on nightlies before the branching instead of doing it at the RC stage, since fixing issues in RCs is a bit more difficult compared to develop. This means that the week leading up to branching will be a stabilization week with no major features being merged during that time, meaning hopefully the RC cycle will also be faster as bugs will be caught earlier. I would be happy to hear other people’s feedback regarding this idea.
In any case, this means that any features planned for 1.20 should be merged by October 8th. So the planned schedule should look something like this:
|1.20 Dev Start||July 16th|
|1.20 Half Way Point||August 30th|
|1.20 Stabilization||October 8th|
|1.20 RC2||November 1st|
To try and plan a bit ahead, I’ve put down a list of some of the more significant feature that are aimed for this release afaik. I’ll make this post a wiki so others can add other features to the list. Please keep in mind this isn’t a commitment that these will all be in the release, but more of an attempt to collaborate on what we are aiming for and prioritize these features.
Planned Features for Foreman 1.20 (Please add others you think should be in):
- Renderer refactoring
- https://github.com/theforeman/foreman/pull/5683 - merged
- Snapshot tests for templates
- GraphQL API
Strong Params enforcementWill most likely not be ready in time
Foreman plugins that closely follow the same schedule (Please add others you think should be in):
- Convert Katello Sync Plans to use Foreman-Tasks
- UX Papercuts
- System Purpose
- Content View Import/Export