Marcos Silva
1.7 KiB
1.7 KiB
What is this MR for?
Problem or feature description.
What does this MR do?
Solution description.
How was it tested?
Describe the steps taken to verify the change works. Name the tests or scenarios.
IMPORTANT: answers like "tested", "checked locally", "tested on dev environment" are NOT acceptable.
Are there points in the code the reviewer needs to double-check?
(Specify any point to pay attention to.)
Does this MR meet the common acceptance criteria?
- Unit tests
- New tests are added on this bug/feature
- All existing tests are passing
- MR name follows the pattern
[UNM-XXX] <short description of what is done>(no separator after the ticket) - Branch name follows the pattern
feature/UNM-XXXX,bugfix/UNM-XXXX, orbugfix/UNM-XXXX_<release> - A person from
MAINTAINERS.mdis set as Assignee; Reviewer left empty unless another approval is required - "Squash commits" option is selected
- Pipeline is green
- All threads are resolved
- Appropriate documentation is created/updated (mandatory for new feature)
- The changes are backward compatible
- There are no merge conflicts with the branch you are merging in
Does this MR meet the feature acceptance criteria?
(Optional. For feature MR only.)
- New feature files or scenarios are added and passing
- Feature MR has been demonstrated to the product owner
- Permission for merge was obtained from the product owner
Related Information
Ticket: Ticket-ID
Where should it be merged?
(master, release/202x.x, etc.)
Is this MR blocked?
(If another MR must be merged first or QA testing is pending, apply the "Do not merge" label and name the blocker here.)