You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Please first check for answers in the [Mbed TLS knowledge Base](https://tls.mbed.org/kb). If you can't find the answer you're looking for then please use the [Mbed TLS mailing list](https://lists.trustedfirmware.org/mailman/listinfo/mbed-tls)**
* Pull requests cannot be accepted until the PR follows the [contributing guidelines](../CONTRIBUTING.md). In particular, each commit must have at least one `Signed-off-by:` line from the committer to certify that the contribution is made under the terms of the [Developer Certificate of Origin](../dco.txt).
3
+
* This is just a template, so feel free to use/remove the unnecessary things
4
+
## Description
5
+
A few sentences describing the overall goals of the pull request's commits.
6
+
7
+
8
+
## Status
9
+
**READY/IN DEVELOPMENT/HOLD**
10
+
11
+
## Requires Backporting
12
+
When there is a bug fix, it should be backported to all maintained and supported branches.
13
+
Changes do not have to be backported if:
14
+
- This PR is a new feature\enhancement
15
+
- 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
16
+
17
+
Yes | NO
18
+
Which branch?
19
+
20
+
## Migrations
21
+
If there is any API change, what's the incentive and logic for it.
22
+
23
+
YES | NO
24
+
25
+
## Additional comments
26
+
Any additional information that could be of interest
27
+
28
+
## Todos
29
+
-[ ] Tests
30
+
-[ ] Documentation
31
+
-[ ] Changelog updated
32
+
-[ ] Backported
33
+
34
+
35
+
## Steps to test or reproduce
36
+
Outline the steps to test or reproduce the PR here.
0 commit comments