this is just an early warning that develop branch for 1.18 is scheduled to branch in 1 month.
This time, I’ll try to contain information regarding 1.18 in a single thread rather than creating a new one for each announcement. This experiment aims to make it easier for people to follow the current release status as they will need to watch only one thread. If we find out that it does not work because the discussion gets too branched out, we can always create new threads.
I wanted to look at what our current support stack is, proposed changes and if there is anything we want to update for 1.18. Experts in these areas, please post corrections. I plan to keep this post “pinned” and updated as we evolve changes.
Does this imply the branch date is moving due to these issues? If yes, can we set a new target date based on estimation to fix them? That will just help with planning even if it moves again rather than having a “as soon as possible” tactic.
I would not consider the SCL update a blocker for branching. I would prefer moving forward when we can.
If we manage to solve everything today, we will not have to postpone branching ;-). I could set a new date, but that would be kind of random, because I have no estimation on how long it will take to fix these issues.
fix for compute attributes is ready and can go in today if it gets ack from a reviewer
@ekohl is trying to do a scratch build without source maps to address the js issue
I found out about ansible stuff just yesterday and I am not sure what is needed there, maybe @dLobatog knows?
I’ll have a look at the Debian side of it and we need to verify if our backup tooling also backs up /var/lib/foreman-proxy. The benefit is that we no longer need to consider /usr/share/foreman-proxy writeable. Since we also modified the REX SSH plugin, I’m also going to verify that still works.
This should no longer be considered a blocker for branching.