Right now, backporting PRs is a manual process that is done by engineers. This is problematic since:
it is prone to error since engineers may forget to backport a PR. This has resulted more than once in features/fixes not landing in track branches and us realising it when this is raised by an issue/stakeholder.
it adds chore work to the development process
Note that automating backports has also been discussed as part of improving the workflow of rock development and integration in #886.
What needs to get done
Define backporting strategy
When and where do we want this to be automated?
How we can ensure that engineers won't forget to use this automation?
Investigate how this can be impleneted
There are bots available that could do this.
We should also ask other teams to see if this has already been implemented by engineers at Canonical
Implement solution
Definition of Done
PRs can be automatically backported in all of Kubeflow team repostiories
Context
Right now, backporting PRs is a manual process that is done by engineers. This is problematic since:
Note that automating backports has also been discussed as part of improving the workflow of rock development and integration in #886.
What needs to get done
Definition of Done
PRs can be automatically backported in all of Kubeflow team repostiories