2017-06-21 13:57:25 +02:00
Notes:
2017-07-24 12:28:48 +02:00
* Pull requests cannot be accepted until:
2017-06-21 13:57:25 +02:00
- The submitter has [accepted the online agreement here with a click through ](https://developer.mbed.org/contributor_agreement/ )
2017-07-24 12:28:48 +02:00
or for companies or those that do not wish to create an mbed account, a slightly different agreement can be found [here ](https://www.mbed.com/en/about-mbed/contributor-license-agreements/ )
2017-06-21 13:57:25 +02:00
- The PR follows the [mbed TLS coding standards ](https://tls.mbed.org/kb/development/mbedtls-coding-standards )
* This is just a template, so feel free to use/remove the unnecessary things
## Description
A few sentences describing the overall goals of the pull request's commits.
## Status
**READY/IN DEVELOPMENT/HOLD**
## Requires Backporting
2017-07-24 14:19:02 +02:00
When there is a bug fix, it should be backported to all maintained and supported branches.
Changes do not have to be backported if:
2017-06-21 13:57:25 +02:00
- This PR is a new feature\enhancement
- This PR contains changes in the API. If this is true, and there is a need for the fix to be backported, the fix should be handled differently in the legacy branch
Yes | NO
2017-07-24 12:28:48 +02:00
Which branch?
2017-06-21 13:57:25 +02:00
## Migrations
If there is any API change, what's the incentive and logic for it.
YES | NO
## Additional comments
Any additional information that could be of interest
## Todos
- [ ] Tests
- [ ] Documentation
- [ ] Changelog updated
- [ ] Backported
## Steps to test or reproduce
2017-07-24 12:28:48 +02:00
Outline the steps to test or reproduce the PR here.