The bug mentioned in these two related questions (94496) and (113527) seems to be fixed in different versions.

On Windows, the bugfix version is 11.0.0. On MacOS, reading the comments, it is 10.4.0.

For each of these questions, I am wondering whether this:

Bug introduced in ... and fixed in 10.4.0 (MacOS) and 11.0.0 (Windows)

would be an appropriate form.

How the bug banner should be written for OS-dependent bugfix version?

From a quick search, OS-dependent bugs do not seem to be an issue, the OS specification being either part of the question (see, e.g., (16683) and (111719)) or part of the banner (see, e.g., (89152)).

Update 1. Following the comment of ilian, I would propose instead something like

Windows: Bug introduced in ... and fixed in 11.0.0

MacOS: Bug introduced in ... and fixed in 10.4.0

Update 2. (Follows QuantumDot comment) Bug banner standardization was discussed before in this post, but the case I mentioned here was not addressed previously as far as I know.

Would there be any advantages of having a standard header for these cases as well?

  • 5
    I would be wary of calling it the same bug, if it is indeed fixed in different releases on different operating systems...
    – ilian
    Sep 12, 2016 at 16:18
  • @ilian Good point, I have updated the question.
    – user31159
    Sep 12, 2016 at 23:29
  • 2
    Is it completely necessary to standardize how we write this note? As long as it is clear, I don't think we really need any sort of standardization. After all, we aren't developing Mathematica.
    – QuantumDot
    Sep 14, 2016 at 0:16
  • 2
    @QuantumDot I saw quite a few posts on Meta about how to deal with bugs questions and how to standardize them. The bug banner idea was initiated in this post, and proposition of its standardization in this one. You can see further discussion about standardization in the comments of the latter.
    – user31159
    Sep 14, 2016 at 13:39
  • @QuantumDot Post updated to make the question clearer.
    – user31159
    Sep 14, 2016 at 14:38


You must log in to answer this question.