blob: c5804436a492528eabbbe49772f74cbcdddb786e [file] [log] [blame] [view]
Ron Eldor4b535132017-06-21 14:57:25 +03001Notes:
Dan Handleyc76a5452020-02-18 17:58:20 +00002* 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).
Ron Eldor4b535132017-06-21 14:57:25 +03003* This is just a template, so feel free to use/remove the unnecessary things
4## Description
5A 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
Simon Butcher6f262c42017-07-24 14:19:02 +020012When there is a bug fix, it should be backported to all maintained and supported branches.
13Changes do not have to be backported if:
Ron Eldor4b535132017-06-21 14:57:25 +030014- 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
17Yes | NO
Ron Eldor05b94982017-07-24 13:28:48 +030018Which branch?
Ron Eldor4b535132017-06-21 14:57:25 +030019
20## Migrations
21If there is any API change, what's the incentive and logic for it.
22
23YES | NO
24
25## Additional comments
26Any 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
Ron Eldor05b94982017-07-24 13:28:48 +030036Outline the steps to test or reproduce the PR here.