Feedback has shown that having similar fields in the release notes
section to the main headings is confusing. This PR simplifies the
sections and removes the release notes section completely.
Changes will be required to the release scripts and the docs to
reflect these changes.
There is confusion with having sub headings below Description.
This commit removes teh Description header completely and promotes
sub headings to full headings.
Some of the notes under each heading have also been updated to
provide better clarity.
Condense multiple options into the main three and summarise what
can go into those 3 types.
Add a test results section.
Add compulsory sections to Release Notes.
Feature might be misinterpreted in some cases. This label should be about
functionality in backward compatible way. That means that this is either
deprecating some current one or adding new functionality.
Functionality change should cover:
- adding configuration
- deprecating functionality
- adding new functionality
This change would go automatically to feature release.
Not only new target, any target update goes to own section. This covers
target updates to SDK, HAL implementation, target list, etc.
All these go to patch releases.
Please use these 2 sections for describing a pull request. They should be part
of every pull request.
The type specifies what is expected from the pull request and when it can be
released. For instance a feature pull request can't be expected to go to the
patch release.
Important: do not mix pull request types !
Changed also the heading type, to make it smaller.