PE: how to respond to bug reports that are nitpicking in nature?

[AaronCQL]

For example, bugs which report

• Minor typos
• Diagrams too large (not that it is too complex, just purely large in size)
• Diagrams too small
• Diagrams too complicated (very debatable)
• Suggestions to reorder sections of the user/developer guide

[okkhoy]

• Suggestions -> Can reject
• Minor typos & Diagram too small -> low severity, accept ('cos affects readability)
• Diagrams too large -> can reject, unless diagram not fully visible in PDF, if latter case, low severity accept
• Too complicated -> accept; severity depends on how you want to defend your choice can be low or medium

[raivatshah]

Thanks prof! Should we accept typos as small as missing a "" character while closing a special typing in ASCII Doc?

[okkhoy]

Probably not. But this is an indication that you need to be careful 😜

[raivatshah]

Haha! Thanks prof! We will be careful in the future!

[CornCobs]

My group accepted issues that were minor typo corrections, formatting or suggestions, as we had no good reason to reject them (We assume that rejecting mean you disagree with the issue raised, but how can we disagree with a typo?)

I assume this will not matter as the tutors will go through the issues eventually?

[okkhoy]

Yes, the teaching team will go through the issues.