Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

explain some more details of the triage procedure #766

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

explain some more details of the triage procedure #766

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7600033
explain some more details of the triage procedure
Aug 29, 2024
e03c809
use monday-sunday weeks
Aug 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions src/release/triage-procedure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,3 +130,11 @@ each PR:

Once you are done triaging PRs, post your report in the topic for the current
week's triage in the `#t-release/triage` Zulip stream.
the topic should have a name like `YYYY-MM-DD to YYYY-MM-DD`.
Note that this uses a monday-sunday week.
if a topic does not exist, you can generate it's title with
the following bash oneliner (requires GNU date):
`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')")"`

#### Avoiding duplicate work
If a PR's labels are still accurate, it can be worth it to remove and re-add a label in order to update the last-modified timestamp, preventing it from turning up in other triagers searches.
Loading