Reviewer 1 wants more about version control and maintainability. We can fend off VC by saying we assume that's being used (and it doesn't directly affect the robustness of the software, though it does affect the dev process), and fend off the second by tightening up our definition of robust: affordable maintenance is important, but out of scope for this paper.
Reviewer 2 wants more emphasis on version control as well. Can we file this as "rule 0"?
Reviewer 1 wants more about version control and maintainability. We can fend off VC by saying we assume that's being used (and it doesn't directly affect the robustness of the software, though it does affect the dev process), and fend off the second by tightening up our definition of robust: affordable maintenance is important, but out of scope for this paper.
Reviewer 2 wants more emphasis on version control as well. Can we file this as "rule 0"?