As bugzilla has no info about entry point, we should apply that patch on top of master and report:
if patch compiles
if patch pass test suite
3 if patch do not decreases code coverage
if patch has any lint problem
(not neccesarily in that order)
We need to notify contributor and maintainer if that patch has any problem (maybe commenting on bugzilla is enough) but to allow maintainer to collect existing patches ready to merge we should find another way (like a state in bugzilla patch)
NOTE: We should comment the hash for master at time patch is applied (or a link to git fork where applied) so if master changes and patch do not apply maintainer can rebase or rework.
When a new patch is added we need to compile that
As bugzilla has no info about entry point, we should apply that patch on top of master and report:
(not neccesarily in that order)
We need to notify contributor and maintainer if that patch has any problem (maybe commenting on bugzilla is enough) but to allow maintainer to collect existing patches ready to merge we should find another way (like a state in bugzilla patch)
NOTE: We should comment the hash for master at time patch is applied (or a link to git fork where applied) so if master changes and patch do not apply maintainer can rebase or rework.