One of our goals in the Release Engineering subproject of SIG Release
is making the cherry-pick experience to release branches easier and
more aligned to the overall release process. There have been
discussions about whether or not it is required to do cherry-picks to
new release branches during the cycle, justified by the fact that we
do not manually fast forward release branches any more since a couple
Based on this discussion, we were working on the creation of an
automatic release branch fast forward periodic job in prow, which is
actually working since yesterday (in mocked mode):
You can see from the latest runs that the job does nothing right now,
because we do not have a release-1.24 branch yet. If the branch gets
created, then the job will sync the release branch and master until we
cut the final tag v1.24.0.
The job does no actual modification to the k/k repository yet, since
we're running it still in mocked mode. Our plan is to graduate the job
to sig-release-releng-blocking with the beginning of the 1.25 release
cycle (mid April) by removing the mocked behavior.
This means for the current cycle: Please still cherry-pick your merged
master PRs into the upcoming release-1.24 branch (planned for April 5)
in the same way we did it in the last cycle.
As a next step we will take care of updating the developer
documentation to reflect the current state. Thank you all and have a
All the best,
- on behalf of SIG Release