search

nus-cs2103-AY2324S2 / forum

16 stars 0 forks source link

Regarding known bugs from developers #898

Open vnnamng opened 7 months ago

vnnamng commented 7 months ago
  1. If the bugs has been caught by the developers in known issues and future implementations, how do we treat them?
  2. If the UG already has cautions and advise against bad inputs, is it still consider a bug when bad inputs create problem?
damithc commented 7 months ago

@vnnamng

image

Known issues given in the UG: There is no immunity. If you think they should have been resolved in the current version itself (i.e., does not qualify for response.NotInScope), you can report them. However, stating them in the UG reduces the severity of the issue.

SherisseTJW commented 7 months ago

Just hopping on here, I'm a bit confused now since the following is mentioned in the website here.

image

Can I check if we will actually be penalized? Since you mentioned it reduces the severity but does not provide immunity.

damithc commented 7 months ago

@SherisseTJW There are two separate things:

  1. 'Planned enhancements' given in the DG -- this is recommended and regulated by course requirements
  2. 'Known issues' given in the UG -- this is something a team might decide to do on their own, and we don't stop them from doing so

Only the first one will not be penalized. The second one does have such immunity.

SherisseTJW commented 7 months ago

Ah, I misunderstood the reply. Thanks for the clarification and apologies to @\vnnamng for hijacking.