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.

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

explain some more details of the triage procedure #766

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

Conversation

lolbinarycat
Copy link
Contributor

based on discussion with @Dylan-DPC

@rustbot
Copy link
Collaborator

rustbot commented Aug 29, 2024

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Dylan-DPC (or someone else) some time within the next two weeks.

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 29, 2024
`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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know why triage does this trick of re-applying labels, but to a reader not familiar with the procedure this may sounds slightly unclear/generic. Can you detail why triage does this? Which label re-apply?

Example: "Since triaging is done sorting by looking at oldest issues first, re-applying the label X or Y will update an issue last-modified timestamp, signaling to other triagers that it has already been talen care of".

@@ -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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if a topic does not exist, you can generate it's title with
if a topic does not exist, you can generate its title with

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')")"`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd probably improve a little bit the formatting because the rendered markdown is a bit cluttered
grafik

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion:

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')")"

Copy link
Contributor

@apiraino apiraino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a few comments, mostly nitpicks.

after them, it looks good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants