Lines Matching refs:should

17 - Contributions should include tests, as mentioned in the [Tests](#tests) and [Continuous Integrati…
18 - The code should be written in a clean and readable style, and must follow [our coding standards](…
19 - The code should be written in a portable generic way, that will benefit the whole community, and …
20 - The code should be secure, and will be reviewed from a security point of view as well.
25 …m/Mbed-TLS/mbedtls) to start making your changes. As a general rule, you should use the ["developm…
28 1. For quick merging, the contribution should be short, and concentrated on a single feature or top…
33 …should not be necessary for a user to make any changes to their own code to work with a newer vers…
48 …a bug fix introduces a change to the API such as a new function, the fix should be reworked to avo…
58 As mentioned, tests that show the correctness of the feature or bug fix should be added to the pull…
64 …s available to show test coverage of the library. New code contributions should provide a similar …
66 Sample applications, if needed, should be modified as well.
70 Once a PR has been made, the Continuous Integration (CI) tests are triggered and run. You should fo…
78 1. All interfaces should be documented through Doxygen. New APIs should introduce Doxygen documenta…
79 1. Complex parts in the code should include comments.
81 1. If a [Knowledge Base (KB)](https://mbed-tls.readthedocs.io/en/latest/kb/) article should be adde…
82 …hub.com/Mbed-TLS/mbedtls/blob/development/ChangeLog.d/00README.md) entry should be added for this …
91 All new files should include the standard SPDX license identifier where possible, i.e. "SPDX-Licens…
93 … by the original authors of the code. Where possible for new files, this should be noted in a comm…
97 … commit message. If more than one person contributed to the commit, they should also add their own…