Skip to content
Snippets Groups Projects
Commit 03812d19 authored by Lydia Pintscher's avatar Lydia Pintscher 🐳
Browse files

add checklist for commits to HACKING

it's supposed to help new contributors make sure they don't forget anything important
please add if something important is missing

CCMAIL: amarok-devel@kde.org
parent 98f3d561
No related branches found
No related tags found
No related merge requests found
The following checklist is supposed to help you make sure you don't forget anything important in a commit.
For every commit:
* Does it conform to Amarok's coding style?
* Is there a feature request, bug report or review request associated with it? (Please close them with the commit message.)
* Does it introduce new dependencies?
* Does it add new strings? Is Amarok in string freeze?
Additionally for commits introducing new features:
* Does it fit Amarok's vision or at least not work against it?
* Who will maintain the code?
* Is Amarok in feature freeze?
* Do existing regression tests still pass?
* Are new tests needed?
* Has it been reviewed by a usability person?
* Does user documentation exist?
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment