[Release process] Improve the initial scope gathering process

[deepakpathania]

Problem statement

The release lead kicks off a release thread where all the leads mention their planned scope at the beginning of each release cycle. This process has a few inefficiencies:

• getting scope from each team requires back and forth by release lead and adds to their responsibilities.
• the scope provided at the beginning of the cycle is not always fleshed out properly.
• current scope just lists GH issues which aren't always obvious to translate to product features.

Acceptance criteria

Improve the current release scope gathering process such that the problems stated above can be resolved/minimised.

Relevant links

• Idea to use GH milestones
  • Example implementation at team level
• Idea to improve current thread with more context
  • Another one