http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8753
--- Comment #189 from Kyle M Hall <k...@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #188) > While I have put coding guideline additions on the agenda a lot of times in > the past, I don't believe that we can ever have a complete set of rules that > will fit every situation and possible question. > > Another common practice we QA has used where they haven't been sure about > something is asking for more opinions - I think this has helped in a lot of > cases to get more views and a better picture of the problem and possible > solutions. That simply highlights the problem. With this methodology, a developer will not know if code will pass qa or not until it has been written and submitted. I agree, we will never have a complete set of rules, but we can build that set as we go. The more we have written down for developers to be aware in advance, the better. We need documented guidelines. The approach of "this doesn't feel right to me" just doesn't work any more. It can only lead to future frustration for developers. We can't have one set of rules for bug A and another set of rules for bug B. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
