Release Post 15.2 Retrospective
Release post MR: !107227 (merged)
Please add your feedback by 2022-07-26. Thank you!
Note for release post team (release post manager, technical advisor, TW lead and release post manager show, and Product Operations): For items you want to cover during the live retro, please add the
If no items have
Create individual comments for every entry so that each item can have its own thread. Then, each thread will get an **Action: @mention**
for resolution tracking.
Start your comment with an H2 heading which will be used as its title, and add the appropriate icon ahead of it to indicate which category it falls under:
## :thumbsup: Something that went well
## :thumbsdown: Something that didn't go well
## :bulb: Something we can improve
## :question: Something for discussion but not a clear good or bad event to improve upon
## :thought_balloon: Something related but not required for closing the retro
How to run the sync retro
The release post manager will schedule/lead the sync after the 22nd and schedule permitting, no later than the 26th:
- RPM opens meeting by asking if folk want to record the meeting, as it's optional
- if recorded, RPM will post the recording in
#release-post-prep
Slack channel
- if recorded, RPM will post the recording in
- RPM screen shares to talk through any items with
⭐ - RPM and any other participants document conversation, action items and assignees of actions in comment threads as needed
How to close this retro
It is the responsibility of the release post manager to track and close this issue in partnership with Product Operations
- During and after release, collect and add threads here from Slack, MRs and other channels as appropriate
- Once the release is over, identity Action and assignee
@mention
for the comment thread - Close each thread with a
✅ emoji after the Action is complete or if no action is required - Prioritize first closing any items that affect the next release post managers workflow, no later than the 1st of the month- Each thread should be actioned with MRs where available or a resolution
- Do not
✅ emoji prior to the Action being complete. A link to an epic/issue/MR pointing to an action can suffice to add the checkmark
Remaining items
-
Don't include social media in stands-up by default. -
Move this step to the 18th as part of content assembly. -
Low MVP engagement -
Part of the process is to Approve any merge requests that you have reviewed.
This is fine for open MRs, but if code has already been merged, it is difficult to coordinate getting an update made, since the original author will have to make a new MR to incorporate feedback. -
We manually fix youtube links that are broken. We know they need to include /embed
in the URL. We should test this in the pipeline. -
Brian runs a script to take deprecations and removals from the docs site and make a bulleted list on the release post page. -
Several tasks are attached to specific times of day but that is not immediately apparent when reading the table of contents or scanning the list of items. -
Should we increase the size limit for GIFs? -
The ordering of tasks in different sections conflict. -
The lint
job frequently is one of the longest running jobs in the pipeline. It should be split into smaller jobs to run in parallel or sped up. -
Can we start adding the number of community contributed MRs and the number of community contributors to the release post? -
@stkerr
added@wspillane
from Social to a number of places he didn't need to be involved -
Why do we have Darren & Dilan explicitly called out in the release post with tasks for Runner/Omnibus/Mattermost? -
What is the significance of doing a merge from master? I was able to successfully rebase onto master with no merge conflicts so there arent any commits to actually merge in at this point -
Do these guidelines make sense for MVP? -
8-month old mp4 files in a yaml-only directory
After retro
- After this retro issue is closed, close the
#15-2-release-post-prep
Slack channel