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

[Week 13] PE bug processing -- follow up post #29

Open
okkhoy opened this issue Apr 18, 2019 · 0 comments
Open

[Week 13] PE bug processing -- follow up post #29

okkhoy opened this issue Apr 18, 2019 · 0 comments

Comments

@okkhoy
Copy link
Contributor

okkhoy commented Apr 18, 2019

Dear students,

Please read the instructions here carefully.

Few things to quickly point out:

  • Don't create random labels or edit the existing labels. Please use the labels that are already created in the repository.
  • Don't simply close the issue after reviewing/processing without assigning a response.* label.
    • All such issues without a valid response.* label will be treated as response.Accepted, i.e., it is a valid bug on your product.
  • If you think an issue is a duplicate of another, assign the duplicate label; in addition, you need to specify the original issue using a Duplicate of #___ annotation as explained here.
  • Assign the type.* label to indicate what type of bug it is.
    • If there is no type.* label, then such bugs are treated as type.FunctionalityBug.
  • Attach an assignee to every bug (even the rejected bugs) to indicate who is the owner of the bug.
    • If there is no assignee, then the responsibility of the bug will be distributed among all the team members (i.e. all team members will lose marks for this).

Please note that you are allowed to change the severity and type of the bug. However, you need to provide an explanatory comment to justify your choice.

Thanks,
Akshay

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant