blob: 485b541952f73d35f4badc683835d4106454f670 [file] [log] [blame] [view]
Ron Eldor4b535132017-06-21 14:57:25 +03001Notes:
Ron Eldor05b94982017-07-24 13:28:48 +03002* Pull requests cannot be accepted until:
Ron Eldor4b535132017-06-21 14:57:25 +03003- The submitter has [accepted the online agreement here with a click through](https://developer.mbed.org/contributor_agreement/)
Ron Eldor05b94982017-07-24 13:28:48 +03004 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/)
Ron Eldor4b535132017-06-21 14:57:25 +03005- The PR follows the [mbed TLS coding standards](https://tls.mbed.org/kb/development/mbedtls-coding-standards)
6* This is just a template, so feel free to use/remove the unnecessary things
7## Description
8A few sentences describing the overall goals of the pull request's commits.
9
10
11## Status
12**READY/IN DEVELOPMENT/HOLD**
13
14## Requires Backporting
Simon Butcher6f262c42017-07-24 14:19:02 +020015When there is a bug fix, it should be backported to all maintained and supported branches.
16Changes do not have to be backported if:
Ron Eldor4b535132017-06-21 14:57:25 +030017- This PR is a new feature\enhancement
18- 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
19
20Yes | NO
Ron Eldor05b94982017-07-24 13:28:48 +030021Which branch?
Ron Eldor4b535132017-06-21 14:57:25 +030022
23## Migrations
24If there is any API change, what's the incentive and logic for it.
25
26YES | NO
27
28## Additional comments
29Any additional information that could be of interest
30
31## Todos
32- [ ] Tests
33- [ ] Documentation
34- [ ] Changelog updated
35- [ ] Backported
36
37
38## Steps to test or reproduce
Ron Eldor05b94982017-07-24 13:28:48 +030039Outline the steps to test or reproduce the PR here.