Re[2]: [PEAR-CORE] Re: [pear-webmaster] Re: cvs: pearweb /public_html/trackback trackback-admin.php

||*()*|| [\..konnichi wa, ogenki desu ka, Greg../] Saturday, October 22, 2005, 5:02:41 PM, you wrote: >> >> GB> I think the answer to this is anyone who experiences a broken webpage as >> GB> a result, no? >> >> GB> The point is that as core PEAR developers, we are held to the same >> GB> standard that others are. >> >> GB> I think the best thing to do is to test prior to commit, or to post a >> GB> patch and ask for testing if it's not possible to test. Committing a >> GB> broken patch is far worse than not committing a possible fix. >> >> Yes, Greg - that's all good in theory. Have you tried to test it yourself? GB> Yes I have. You have to click through every page (with display_errors GB> on and so on), and try uploading/deleting releases. It takes 5 minutes. GB> I do it every time I commit something to pearweb. Well, have you tried to test register_globals off impact? I doubt it is possible to test this thoroughly by one peson, but with the help of other devs it can be done. But this must be backed up with convenient way to report problem and detailed explanation why it is necessary - not by just another email to "test this as much as possible". I wonder how many replies have you got per such email? =) WBR.techtonik -- (B)uilding, (A)ntenna, (S)pan and (E)arth * terminal velocity - 54m/s, 305m *