MATLAB: How to find when a feature was introduced in MathWorks products?

Once I wanted to find when = in which MATLAB Release the Fast Restart feature of Simulink was introduced.
This post explains the way to find it out.
1.) Go to the MathWorks product documentation http://www.mathworks.com/help/
2.) Search for "fast restart" (with quotation marks around)
3.) On the left under "Refine by Product" select Simulink
4.) On the left under "Refine by Type" select Release Notes

Direct link looks like this: http://www.mathworks.com/help/search.html?qdoc=%22fast+restart%22+type%3Arn+product%3Asimulink

5.) Click on the one remaining search entry and you should find what you are looking for.

StackOverflow https://stackoverflow.com/questions/19778832/how-can-i-check-since-which-matlab-version-a-function-exists/36922759#36922759

FileExchange Utility when

MathWorks Bug Transparency and MATLAB R2015b bug in fullfile

There is a bug in MATLAB R2015b in the fullfile function:

>> fullfile('C:\', '\titi\toto.m')

ans =

C:\\titi\toto.m

See the doubled backslash after the drive letter (highlighted in red).

The function JoinPath by Jan Simon in the FileExchange fixes it.
Jan states his function is also faster. I haven't verified this but I trust him.

It seems this bug hasn't been reported yet (as of 2016-07-19/ I've just reported it).

After exchange with the MathWorks support, it seems this bug was reported but MathWorks does not publish all known bugs under http://www.mathworks.com/support/bugreports/. (I would have expected that.)

Below the explanation from MathWorks Support (answer date: 2016-07-20)

This bug is only registered internally and was not nominated for an external bug report.
...
There is a decision making process (including the 'nomination' I mentioned) involving considerations of how many customers might be impacted and the severity of the issue. In this specific case, you are the second customer worldwide coming to us since existence of the bug. We in Technical Support would not be able to convince Development, that this bug impacts a larger user base.