Research: Drafting and reviewing release post item content blocks in feature issues rather than MRs
Currently PMs do initial draft and reviews of all release post items content blocks in individual MRs on master. As we shift toward boosting our in product release notes, per &583 (closed) and related issues #7315 (closed) & Product#1145 (closed), we would like to decouple the production dependency of product release notes from the marketing blog post. The benefit here will be that we'll continually have updated product release notes in Gitlab, and the marketing blog post will can generate at which ever cadences it chooses by pointing to a repository of continually updated release notes, rather than being dependent on individual MRs.
To execute on this, per issue gitlab-org/gitlab#217145, the Release team is considering tagging/pulling content directly from feature issues. It would be great if we could align the release post process with this for efficiency/overhead of effort, as well as consistency of SSOT.
If we were to have PMs start drafting, doing reviews and finalizing their release post item content in feature issues rather than MRs:
-
How would we need to modify feature and recurring issue templates (e.g. additional tags/label)? @jramsay @fseifoddini !56446 (merged)
-
How would the review process work for (e.g. the checklists and reviews that happen here in MRs? @fseifoddini -
How would the currently leveraged content assembly script/process need to be modified? (e.g can the release post branch on the 18th assemble from issues via tags/labels, or would we need to push in to MRs or point to a repository via the in product release notes or...?) @jeanduplessis @ericschurter