diff --git a/E-needs-test.png b/E-needs-test.png new file mode 100644 index 00000000..cc202a47 Binary files /dev/null and b/E-needs-test.png differ diff --git a/index.html b/index.html index 8d8dcb1b..d60a466c 100644 --- a/index.html +++ b/index.html @@ -110,6 +110,11 @@ https://github.com/Nilstrieb/cargo-minimize + + adding tests + bug has been fixed, but no test added + just commit a test to close the issue! + ## existing unstable features diff --git a/speaker_notes.md b/speaker_notes.md index 5e9a3a30..ca51ba97 100644 --- a/speaker_notes.md +++ b/speaker_notes.md @@ -37,4 +37,13 @@ Triaging issues is great because it's easy to get started and you can put in ver You can triage one issue in two minutes, or you can spend 2 hours on an issue. It always depends on the issue and how much time you want to put in, even the small work is nice. -For issues \ No newline at end of file +Some of the things that are involved when triaging issues are labelling, minimization, bisection and adding tests. + +Labelling is the task here that takes the least time. We have an example issue here, that requests that the standard +library documents the memory ordering guarantees for the thread spawn function. +Let's think about what this is: This is a *feature request* for *documentation* about *threads* and *atomics*. +The feature request is to the *library API team*, as it's about a guarantee. + +So we add those labels. Remove needs-triage, as we're doing triage, add the docs, thread and atomics area, the category +feature request and the team libs api. If you're not part of a team that has write access to the repository, you can leave +a comment with rustbot as shown here. If you're interested and want to know more, see the link below. \ No newline at end of file
bug has been fixed, but no test added
just commit a test to close the issue!