Add general style guidance based on the Release Note Improvement Initiative, Working Group 1

[jafiala]

Issue:
The current guidance for writing release notes was insufficient; we propose expanding this section with general guidance that should address commonly encountered problems in RN texts.

Additional information:
Draft prepared by Ingrid Towey, Darragh Fitzmaurice, James Smith, Brian Angelica, Jan Fiala

[IngridT1]

LGTM

[jafiala]

Remove IBM Style links

[jafiala]

Aligning terminology

[bergerhoffer]

Sorry for the delay, I've added some feedback.

In addition to this, I was wondering whether there was any further guidance coming on writing release notes. A few things that came to mind are recommending to link to existing doc content for more information on a feature, etc. Or recommendations on how much detail to go into in the release note - I assume we prefer to be concise (sometimes cut out excessive technical detail), but maybe that's just my personal preference.

Also, we mention several categories, but do have any preferred order or actual names that we want each category to be named, so that teams are doing so across products?

[jafiala]

Sorry for the delay, I've added some feedback.

In addition to this, I was wondering whether there was any further guidance coming on writing release notes. A few things that came to mind are recommending to link to existing doc content for more information on a feature, etc. Or recommendations on how much detail to go into in the release note - I assume we prefer to be concise (sometimes cut out excessive technical detail), but maybe that's just my personal preference.

Also, we mention several categories, but do have any preferred order or actual names that we want each category to be named, so that teams are doing so across products?

Thank you Andrea, I will go through your suggestions!

We have additional guidance in progress specifically on RN types and the chapters they are in, as well as a template for a RN document (which should be useful mainly for new products). Recommendation to link to existing product docs is part of the new feature/enhancement type. I think some additional guidance on being concise and cutting overly technical details is also a good idea, I'll add it into the general points.