Add RPC deprecation process
Merge request reports
Activity
Should we add the deprecation template as a description template in the repo?
Good question, I was not fully aware of that feature.
The downside of that would be that we'd have two sources for this template, and situations where one gets updated but the other doesn't. There is no magic monkey that keeps what we write in markdown in this git repo in sync with the settings of the gitaly project. :)
@andrewn How do you propose we deal with updates to the issue template if it's stored as a project setting on gitlab.com?
@andrewn I propose we don't use issue templates for this. We are not dealing with massive amounts of deprecation issues so that we need to make submission more convenient. It is more important to have a clearly documented process, and issue templates in the app go against that. Do you agree?
added 8 commits
enabled an automatic merge when the pipeline for 96297cfa succeeds
mentioned in commit 085d747c
