Review the bug reports received by your team

[ccristina]

Dear Students,

• Bugs filed during the PE have been transferred to a different centralized repository and are ready for review/processing now. They can be found at https://github.com/nus-cs2103-AY1819S2/pe-results/issues
• To find bugs reported on your product, filter by tutorial.* and team.* labels.
• Deadline for processing the bugs is Monday 22 April 2019, 11:59 PM.

Before processing the bugs, carefully read the instructions here: https://nus-cs2103-ay1819s2.github.io/cs2103-website/admin/project-deliverables.html#processing-pe-bug-reports%3A-2.

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: https://help.github.com/articles/about-duplicate-issues-and-pull-requests/
• 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.

Best regards, Cristina.

[lingyanhao]

I am unable to access the repo and got a 404. Is anyone else facing the same issue?

[ccristina]

You should see it now! Check again!

[Jackimaru96]

Will bug reports that are 'insincere/random' be penalised and can the team reviewing the bug reports report if we deem them to be insincere?

[okkhoy]

@Jackimaru96 What do you mean?

[Jackimaru96]

@Jackimaru96 What do you mean?

Thank you for your reply Prof @okkhoy I meant for bug reports that didn't put in effort to show how it can be reproduced/ for example purposely used parameters that are already stated to not be used in the UG like for example input values like 05.50 instead of 5.50

[okkhoy]

Well, without any other context, this particular example is a bug. You should handle such inputs in your code, irrespective of documenting it.

This can also be reproduced, just use 05:50 instead of 5:50 as input.

An example of Cannot be reproduced could be something like just one screenshot without any explanation.

[Jackimaru96]

Well, without any other context, this particular example is a bug. You should handle such inputs in your code, irrespective of documenting it.

This can also be reproduced, just use 05:50 instead of 5:50 as input.

An example of Cannot be reproduced could be something like just one screenshot without any explanation.

@okkhoy Thank you for the clarification