• What strategy to go with for different MRs (Major / Minor versions)
• We recently started assigning MRs again during sprint planning
• Major updates MRs affect a single dependency, so they are easy to address usually. Often it's also possible to find which areas of the app are affected and test only them. It's even easier for dev dependencies as they usually require very little testing.
• Minor and Patch MRs affect multiple dependencies. It could take some time to solve eventual problems caused by the updates. Currently these MRs also require a full regression test (FRT) by QE before getting released. This is problematic as FRT only happens every 2 sprints, so in the worst case these MRs could get stuck for 1~2 months. It doesn't make much sense as minor and patch releases happen frequently, we risk that when we close the ticket the update is already "old". We need to improve this. In theory minor and patch updates must not introduce breaking changes according so semver. It could be safe to promote them if CI is green without testing the whole application. This is a discussion to have with QE too.
• Sometimes reviewing a Renovate MR is not trivial. Especially if it involves peer dependencies or some changes in the code affecting areas with no test coverage. Is this a problem? Should it affect how we assign renovate MRs? 
• In theory every Renovate MR should have a corresponding Jira ticket. This is because of the "cherry-picking" release. Right now each dev assigned to a renovate MR should create the ticket. 
• Create a doc and share with the team for discussion
• Identify pros and cons of different strategies

Additional Ask:

• Investigate on automation to create Jira tickets automatically when a new Renovate MR is created

Self Notes

How should we address Renovate MRs?

• Should we automate a system which creates a ticket corresponding to the Renovate MR created?
• Should it be automated?
• Should we assign them manually? If so, who should be responsible to assign them?

Related Docs

Strategies Investigation Doc [Done]

Strategy Concrete Ideas doc [In Review]

Strategy Suggestions [In Progress]

After this task is finished and we have decided on a clear strategy, the relevant documentation needs to be updates:

• Promotion Manager Duties ?