Preparing 10.5.0 RC1 with only Object Storage related changes
We will probably today/tomorrow have almost all changes that we need for OS. Could we prepare RC1 with just these changes?
There will be: uploads on OS, traces as artifacts, traces on OS, proxied download from OS for artifacts. This is a big chunk and I would be glad if we could work and verify that separately.
This would mean creating a 10-5-stable branch from the current 10-4-stable branch and picking the required commits.
Given that today is 5th of the month, and the code freeze is 2 days away, my question is whether this is worth the effort?
Few questions come to mind:
- Will all MR's that need to be picked apply cleanly on 10.4 branches?
- What will happen with we need to merge master into the stable branches?
- If something is found, how do we get the fixes in quickly and not block the RC?
@markglenfletcher @ibaum What is your opinion on this?
@rspeicher what are the traps we can fall into if we decide to do this?
@smcgivern @mbergeron @ayufan @dosuken123 can you link the MR's that you would want to have in a separate RC? Do you know if they would apply cleanly to current 10-4 stable?