OS-X already renamed to macOS

[Punpun1643]

[nus-se-script]

Team's Response

The use of this name is consistent with the textbook:

Hence, we believe this to be consistent with the constraints placed upon our (and indeed, all) tP projects.

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: Firstly, OX-S is removed and renamed for a while already (since 2016 I believe) to macOS. Bugs from AB3/textbook will also be considered a bug based on the module policy; rejecting them is not justified. Just because something is written inaccurately originally doesn't mean that it should be left as it is. Readers who read the DG do not know what the module policies are given that the DG is on the internet and it can be read by anyone, not just people who are taking/took this module. No one refers to macOS as OS-X already, and writing this for the general audience is just weird; they may not understand what it is referring to. Please also refer to module policy on bug inherited from AB3:

Secondly, there have been multiple reports on this as well in previous AY based on these bug reports example 1 and example 2 all of these are accepted as a bug with the same severity and type that I have reported (i.e. DocumentationBug & VeryLow). Given that they were also taking the same module under the same tP constraints, if these bug reports are accepted, I do not see why my bug report is justified to be rejected.

Lastly, I think this is not justified as not in scope based on the module policy as it does not satisfy any of the two pointers below:

---