Sign off on patches
From Koha Wiki
Koha > Community > Participation
Koha > Technical > Development
Koha > Technical > Development > Coding guides
Koha > Technical > Development > Git
A note about signing off on patches
Signing off on a patch means that the tester has confirmed the following:
- They have stepped through any available test plan
- They confirmed the functionality is working
- They noted any anomalies and determined whether or not these block the patch from going into the next stage of QA.
A person signing off on a patch is responsible for making sure that the functionality is working as described in the patch (but we know that people miss stuff - that's OK! Just be willing to re-do your sign-off for any revisions and no one will complain at you).
On the other side, if you discover any problems with the patch, don't feel afraid to set the bug status to 'Failed QA' and leave a note about your findings.
Method 1: Using sandboxes
The community provides Sandboxes to test easily patches without any technical requirements.
You will not need to install anything on your computer.
Method 2: Using git bz
If you have a working Koha installation (a KohaDevBox for instance), you will be able to sign off patches easily using git bz.
git bz helps a lot in testing patches. There is a dedicated page explaining how it works.
Method 3: "Manually"
There is no good reason to do it this way, but in case git-bz is not working for you, you could do the following.
Download the patch
You can download the patch from Bugzilla using wget or fetch:
$ wget -O <name_of_patch_file> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=<attachment_number>
Or you can save it from your e-mail.
Apply someone's patch to your local Koha repository. You should create a new branch for this purpose.
$ git checkout -b qa_bug_xxxx $ git am -3 -i -u <name_of_patch_file>
You test it.
You might want to add [SIGNED-OFF] to the title/subject of the commit.
git commit --amend
The subject line of the commit email will be taken from the first line of the commit. You can add [SIGNED-OFF] to the beginning of the first line while amending the commit, or you can do so during the "format-patch" process as described below.
If the patch is ok, you prepare a new one with your sign-off. -s = signoff
$ git format-patch -s origin/master
If you did not amend the commit to include "[SIGNED-OFF]" in the previous step, you can do so now:
$ git format-patch -s --subject-prefix='PATCH] [SIGNED-OFF' origin/master
On Bugzilla, you should now update the status of the relevant bug from "Needs Signoff" to "Signed Off". You should also upload your signed-off patch as attachment and mark the initial one as obsolete.
- Sign off on a pushed branch
- Bugzilla report of bugs that currently need a sign off
- Fixing whitespace when applying patches with git