Skip to content

Commit

Permalink
Merge pull request #245 from adamfarley/add_names_to_copied_actions_i…
Browse files Browse the repository at this point in the history
…n_retro_template

Update retrospective template
  • Loading branch information
andrew-m-leonard committed Sep 1, 2023
2 parents 8955f92 + f08174d commit fcaa984
Showing 1 changed file with 11 additions and 13 deletions.
24 changes: 11 additions & 13 deletions .github/ISSUE_TEMPLATE/retrospectives.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,31 +15,29 @@ 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.

**Time, Date, and URL**

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.

0 comments on commit fcaa984

Please sign in to comment.