mirror of
https://github.com/yuzu-emu/mbedtls
synced 2024-11-24 09:48:31 +00:00
69feadc782
The Mbed TLS project no longer requires a CLA. Contributions from now on must be made under both Apache-2.0 AND GPL-2.0-or-later licenses, to enable LTS (Long Term Support) branches of the software to continue to be provided under either Apache-2.0 OR GPL-2.0-or-later. Contributors must accept the terms of the Developer Certificate of Origin (DCO) by adding a Signed-off-by: line to each commit message. The software on the development branch continues to be provided under Apache-2.0. Update README.md, CONTRIBUTING.md and pull_request_template.md to explain the new licensing model. Add a copy of the DCO to the project. Signed-off-by: Dan Handley <dan.handley@arm.com>
1.2 KiB
1.2 KiB
Notes:
- Pull requests cannot be accepted until the PR follows the contributing guidelines. 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. - 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
When there is a bug fix, it should be backported to all maintained and supported branches. Changes do not have to be backported if:
- 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
Which branch?
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
Outline the steps to test or reproduce the PR here.