From f08174db47b4e01a55a8331e2ab44d5c0f719b7b Mon Sep 17 00:00:00 2001 From: Adam Farley Date: Fri, 1 Sep 2023 14:47:26 +0100 Subject: [PATCH] Update retrospective template Signed-off-by: Adam Farley --- .github/ISSUE_TEMPLATE/retrospectives.md | 24 +++++++++++------------- 1 file changed, 11 insertions(+), 13 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/retrospectives.md b/.github/ISSUE_TEMPLATE/retrospectives.md index e94543e..5417118 100644 --- a/.github/ISSUE_TEMPLATE/retrospectives.md +++ b/.github/ISSUE_TEMPLATE/retrospectives.md @@ -15,7 +15,7 @@ All community members are welcome to contribute to the agenda via comments below This will be a virtual meeting after the release, with at least a week of notice in the #release Slack channel. -On the day of the meeting the agenda items will be iterated over, with a list of actions added in a comment at/near the end. +On the day of the meeting we'll review the agenda and add a list of actions at the end. Invited: Everyone. @@ -23,23 +23,21 @@ Invited: Everyone. Time: Date: - URL: -Dial-in: -PIN: **Details** Retrospective Owner Tasks (in order): -- [ ] Post this issue's URL on the \#Release Slack channel around the start of the new release. -- [ ] Copy actions from the previous retrospective into this issue, while ignoring actions that are ticked or have issue links (i.e. clearly-completed actions). -- [ ] Wait until 90% of all builds have been released, with no clear signs of additional respins. -- [ ] Announce the retrospective Slack call's date + time on \#Release at least one full week in advance, and send out meeting invites. -- [ ] Host the slack call for the retrospective, including: - - [ ] Iterating over the actions from the previous retrospective issue, ticking off completed items. - - [ ] Iterate over the agenda, ensuring everything gets debated. - - [ ] Create a clear list of actions at the end of the retrospective, including volunteer names. +- [ ] Post retro URL in \#Release around the start of the new release. +- [ ] Copy actions from previous retrospectives into this issue, ignoring anything ticked. + - Include owner names. +- [ ] Wait until most builds are released, with no clear signs of additional respins. +- [ ] Announce the retrospective's date + time on \#Release a week before. +- [ ] Host the retrospective: + - [ ] Tick completed actions from last retrospective/s. + - [ ] Go through the agenda. + - [ ] Create a tickable list of actions with owner names. - [ ] Create a new retrospective issue for the next release. -- [ ] Set yourself a calendar reminder so that you remember to commence step 1 (in the new issue) just before the next release. +- [ ] Set a calendar reminder so you remember to do step 1 before the next release. - [ ] Close this issue.