<Project Name> <Release Name> Release Notes¶
Abstract¶
Preface to what this document is about
License¶
Include Licensing information here
Version History¶
Contents¶
<Project Name> <Release Name> Version¶
Module version changes¶
List module level version changes
Document Version Changes¶
Changes in documentation
<Project Name> <Release Name> Compatibility¶
Compatibility with Previous Releases¶
<optional, required if there’s a previous release> Is it compatible? Did anything about how a user or developer would consume it change? If so, document it here.
Migration from Previous Releases¶
<optional, required if there’s a previous release for the project>
Describe any special step somebody would have to take to migrate from a previous release to this one. If migration isn’t supported for some combinations, state that as well.
<Project Name> <Release Name> Bugs¶
Resolved Bugs¶
List open and resolved bugs if any.
JIRA TICKETS:
| JIRA REFERENCE | SLOGAN |
| JIRA: APEX-86 | Need ability to specify number of compute nodes |
Deprecated and Removed Capabilities¶
Provide information about the capabilities that are removed or deprecated in this release.
JIRA TICKETS:
| JIRA REFERENCE | SLOGAN |
| JIRA: APEX-86 | Need ability to specify number of compute nodes |
Known Limitations¶
Provide information about the capabilities that are removed or deprecated in this release.
JIRA TICKETS:
| JIRA REFERENCE | SLOGAN |
| JIRA: APEX-86 | Need ability to specify number of compute nodes |
Open Bugs¶
List any remaining open bugs. Ideally provide a short description and a link to the entry in JIRA
JIRA TICKETS:
| JIRA REFERENCE | SLOGAN |
| JIRA: APEX-86 | Need ability to specify number of compute nodes |
<Project Name> <Release Name> Deliverables¶
Software Deliverables¶
List out the software deliverables
Documentation Deliverables¶
Call out the documentation deliverables
<Release Name> Scenario Release Notes¶
<Project Name> <Release Name> References¶
List references
