Pilot: Draft release post blog content blocks in Issues and Epics

We are piloting drafting content blocks (release notes creation) in Issues as part of the overall effort to:

1. improve the release post process for PM contributors
2. create a better repository/SSOT of release notes as part of our Release feature
3. improve issue content by working backwards as it’s one of our most viewed/valuable sources of info both internally and externally to customers/users.

As part of www-gitlab-com#8025 (closed) @jramsay created a script to test pulling content blocks directly from issues to generate the necessary MRs for the release post blog. We need 10 PMs to watch this overview video and follow this proposed process for 13.3 and 13.4.

What will be expected of PM participants?

• Share any feedback/ideas/questions you have in this issue (so we can help you and also learn what wrinkles we need to iron out)
• Participate in any surveys that come your way about this pilot

Important notes:

• It is recommended you use the feature proposal template
• It is recommended you draft and add the content blocks to your Issue at the time of kickoff or earlier
• The script will look for and pull all content under Release Notes in the template, until it reaches the next header
• At this time, you do not need to worry about any discrepancies in between the content block in the Issue vs the final content block that lands in the release post blog after undergoing updates during the review process in the MR