Skip to content

Commit 6dd73e2

Browse files
explain some more details of the triage procedure (#766)
Co-authored-by: apiraino <[email protected]>
1 parent f5548da commit 6dd73e2

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

src/release/triage-procedure.md

+15-1
Original file line numberDiff line numberDiff line change
@@ -131,4 +131,18 @@ each PR:
131131
reviewer commented).
132132

133133
Once you are done triaging PRs, post your report in the topic for the current
134-
week's triage in the `#t-release/triage` Zulip stream.
134+
week's triage in the `#t-release/triage` Zulip stream. the topic should have a
135+
name like `YYYY-MM-DD to YYYY-MM-DD`. Note that this uses a monday-sunday week.
136+
137+
If a topic does not exist, you can generate its title with the following `bash`
138+
one-liner (requires GNU date):
139+
140+
```bash
141+
echo "$(date -I --date="$([ "z$(date +%a)" = "zMon" ] && echo 'today' || echo 'last monday')") to $(date -I --date="$([ "z$(date +%a)" = "zSun" ] && echo 'today' || echo 'next sunday')")"
142+
```
143+
144+
#### Avoiding duplicate work
145+
146+
Since triaging is sometimes done by looking at oldest issues first, re-applying
147+
one of the `S-*` labels will update an issue/PR's last-modified timestamp,
148+
signaling to other triagers that it has already been taken care of.

0 commit comments

Comments
 (0)