Improve issue template for Backport request
As I see at the moment, the backport request issue template is quite simple (e.g.), comparing to a security issue template (e.g.). Take into consideration that:
- Patch release and security release are one now - patch release
- We have a very good runbook for patch release, which has all the details about what to do step-by-step
I suggest that we migrate/merge the runbook to the issue template. It has two benefit:
- Keep the runbook/document close to the tooling
- Provide a detailed step-by-step to the engineers working on the patch releases, without hand holding from RMs
Exit Criteria
-
Backport request issue template has a list of step-by-step, similar to the security issue template
Edited by Dat Tang