DescriptionAnjana Suparna Sriram
2018-02-26 07:39:37 UTC
As Release Notes is new guide for RHHI 2.0 release, 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 doctype to one of the following:
* bug fix - for notable bug fixes that have significant impact on customers
* enhancement - for new features and major enhancements, RFE bugs
* technology preview - for new features shipped as tech previews
* known issues - 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.
----
**Candidates for inclusion**
* Bugs with a customer case attached
* Major new features and enhancements
* Bugs with significant impact on users
* Urgent or high priority bugs
* Fixed known issues
The released release notes is verified and it has all the required information.
Its not customary to move the tracker to verified, but as the tracker is ON_QA, moving it to verified to indicate that the release notes is verfied at the customer portal