Feature #1462

enforce zero tolerance for warnings

Added by wuttke about 3 years ago. Updated about 3 years ago.

Status:RejectedStart date:13 Jun 2016
Priority:LowDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Now that we have achieved (under all platforms???) zero warnings, we should maintain this state. At least in branches develop and master. Especially so if merging into develop will be made conditional on code review.

If new warnings arise, policy should be: Either fix them, or create an issue and temporarily disable the warning.

If we agree on this, then we should have a script (whether among our tests or as a git hook does not matter much) that checks absence of warnings from Swig and Doxygen. For g++, "-Werror" will do.

History

#1 Updated by pospelov about 3 years ago

  • Parent task deleted (#1447)

#2 Updated by wuttke about 3 years ago

  • Status changed from Rfc to Rejected

This question will naturally come up again when configuring the build server. No need to keep this issue open here.

Also available in: Atom PDF