Bug 2388233

Describe the issue: 9.0 Release Notes tracking ticket

Release Notes Process: https://ibm.box.com/s/c375p1saxo9bagxur1d2jorjjaghjg4k

This tracker bug is not a tracker just for known issues but for every change that should appear in the Release Notes - major updates, technical previews, deprecated functions, and so on.

If there is a change that does not have a separate bug (for example it is a change introduced in a rebase), add that rebase bug as a blocker and specify the nature of the change in the doc text field of that bug.


**How to let us know that a bug should be documented in the Release Notes**

1) Add the BZ number of the bug that needs to be documented to the "Depends On" field in the Release Notes tracker bug. Alternatively, add the tracker bug BZ number to the "Blocks" field in the bug that needs to be documented.

2) In the bug that needs to be documented, set the Doc Type to one of the following:

* Bug Fix - for notable bug fixes that have a significant impact on customers
* Enhancement - for new features and major enhancements, RFE bugs
* Technology Preview - for new features shipped as tech previews
* Known Issue - for the known issues found in this release

3) In the bug that needs to be documented, fill in the Doc Text field with the initial information. Use the template that is in the field.

Note: If you can't see the Doc Type and Doc Text fields, make sure to click Show Advanced Fields.

For JIRA tickets: 
If you have Jira tickets that should be included, just mention them in the bug comments and include the needed information in the engineering ticket description.


**Candidates for inclusion**

* Bugs with a customer case attached (Known issues)
* Major new features and enhancements
* Bugs with a significant impact on users
* Urgent or high-priority bugs
* Fixed known issues (bug fixes)