Re: CS fixes

From: Date: Wed, 25 Feb 2004 15:46:45 +0000
Subject: Re: CS fixes
References: 1 2 3 4  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-666@lists.php.net to get a copy of this message
Hi Toby/Lukas, You are both right. We should not do fixes for people, but we should let people know that CS is not optional. If a release occurs after the whitespace issues are pointed out, and the whitespace isn't fixed, QA could simply remove the release. This will both give developers the chance to either say 1) I don't have time to fix, do it for me 2) I will fix it, thanks 3) I am clinically insane, screw you, I like to eat dirt, I'll never fix the CS I don't think we'll see much of #3. :) Greg Tobias Schlitt wrote:
Hi Lukas! <quote who="Lukas Smith">
I dont think it is feasible to have QA commit whitespace fixes if the maintainers dont want this to happen. The internals people are having frequent flame wars about this topic and I want to evade it by making this an optional service instead of a PITA.
Mmmmhhh... On the one hand I have to agree with that. But on the other hand we have those coding standards and nobody should complain about us forcing them to be keeped. What I do not want is to get people thinking "ahh... those QA guys... they offer a nice service for us...". QA should IMHO become in institution of PEAR with a specific range of real power to get quality into PEAR. So this CS issues can become a kind of precedence case. Regards, Toby


« previous php.pear.qa (#666) next »