• New functionality

• Changes to existing functionality

When a new feature or change introduces a reported incompatibility between versions, the Compatibility Considerations subsection explains the impact.

Compatibility issues reported after the product is released appear under Bug Reports at the MathWorks Web site. Bug fixes can sometimes result in incompatibilities, so you should also review the fixed bugs in Bug Reports for any compatibility impact.

The MathWorks offers a user-searchable Bug Reports database so you can view Bug Reports. The development team updates this database at release time and as more information becomes available. This includes provisions for any known workarounds or file replacements. Information is available for bugs existing in or fixed in Release 14SP2 or later. Information is not available for all bugs in earlier releases.

Access Bug Reports using your MathWorks Account.

This section lists commands removed or in the process of being removed. Commands typically go through several stages across multiple releases before being completely removed. This provides time for you to make adjustments to your code.

• Announcement — The Release Notes announce the planned removal, but there are no functional changes; the command runs as it did before.

• Warning — When you execute the command, it displays a warning message indicating it will be removed in a future release; otherwise the command executes as it did before.

• Error — When you execute the command, it produces an error. The error message indicates the command was removed and suggests a replacement command, if one is available.

• Removal — When you run the command, it fails. The error message is the standard message when MATLAB does not recognize an entry.

Commands might be in a stage for one or more releases before moving to another stage. Commands are listed in the Commands Being Removed section only when they enter a new stage and their behavior changes. For example, if a command displayed a warning in the previous release and errors in this release, it appears on the list. If it continues to display a warning, it does not appear on the list because there was no change between the releases.

Not all commands go through all stages. For example, a command's impending removal might not be announced, but instead, the first notification might be that the command displays a warning.

The Release Notes include actions you can take to mitigate the effects of command removal, such as adapting your code to use a replacement command.