Checklist for code review and releases

[troglobit]

Description

After the v24.10.0 snafu (see #736) I thought it was a good idea to start a discussion about having a checklist (reminders) for maintainers:

• Checklist for Code Review (PRs)
• Checklist for Releases

https://github.com/kernelkit/infix/blob/checklist/.github/CHECKLIST.md

Checklist

Tick relevant boxes, this PR is-a or has-a:

• [ ] Bugfix
  • [ ] Regression tests
  • [ ] ChangeLog updates (for next release)
• [ ] Feature
  • [ ] YANG model change => revision updated?
  • [ ] Regression tests added?
  • [ ] ChangeLog updates (for next release)
  • [ ] Documentation added?
• [ ] Test changes
  • [ ] Checked in changed Readme.adoc (make test-spec)
  • [ ] Added new test to group Readme.adoc and yaml file
• [ ] Code style update (formatting, renaming)
• [ ] Refactoring (please detail in commit messages)
• [ ] Build related changes
• [X] Documentation content changes
• [X] Other (please describe): process

[jovatn]

My two cents. Sometimes a documentation change could render a Changelog update. An example is the recent documentation fix for QoS. Thus, it may be a good idea to have a subentry checkbox for Changelog to the Documentation checkbox.

Alternatively, one could consider documentation fixes as bug fixes, but I still think there are cases where you rather wish to check documentation and changelog.

[troglobit]

My two cents. Sometimes a documentation change could render a Changelog update. An example is the recent documentation fix for QoS. Thus, it may be a good idea to have a subentry checkbox for Changelog to the Documentation checkbox.

Alternatively, one could consider documentation fixes as bug fixes, but I still think there are cases where you rather wish to check documentation and changelog.

Agreed, adding a sub-entry checkbox to the pull_request_template.md.