29 lines
912 B
Markdown
29 lines
912 B
Markdown
# Motivation
|
|
<!-- Briefly explain what the change is about and why it is desirable. -->
|
|
|
|
# Context
|
|
<!-- Provide context. Reference open issues if available. -->
|
|
|
|
<!-- Non-trivial change: Briefly outline the implementation strategy. -->
|
|
|
|
<!-- Invasive change: Discuss alternative designs or approaches you considered. -->
|
|
|
|
<!-- Large change: Provide instructions to reviewers how to read the diff. -->
|
|
|
|
# Checklist for maintainers
|
|
|
|
<!-- Contributors: please leave this as is -->
|
|
|
|
Maintainers: tick if completed or explain if not relevant
|
|
|
|
- [ ] agreed on idea
|
|
- [ ] agreed on implementation strategy
|
|
- [ ] tests, as appropriate
|
|
- functional tests - `tests/**.sh`
|
|
- unit tests - `src/*/tests`
|
|
- integration tests
|
|
- [ ] documentation in the manual
|
|
- [ ] code and comments are self-explanatory
|
|
- [ ] commit message explains why the change was made
|
|
- [ ] new feature or bug fix: updated release notes
|