[development] E_ALL mode

[Chris Kennedy]

I am willing to help with coordination and submission of patches to
achieve E_ALL compliance in core, but I'm not personally going to take
an asynchronous approach. It simply isn't an efficient use of my time.
http://drupal.org/node/103250 is ready to fix a solid batch of errors
but has received almost no attention over the past month.

Once that is committed I will go through a round of testing and submit
another patch for key post-install functionality, repeating until
finished. Any development+testing assistance is very welcome, but I'm
not going to waste time maintaining multiple E_ALL patches in a dynamic
HEAD environment if no one is willing to test and review them.

.ck

andrew morton wrote:
> On 1/23/07, Karthik <narakasura at gmail.com> wrote:
>> Can we please restrict notices to the watchdog at least until FAPI is
>> made E_ALL compliant? It is currently rather counter-productive.
> 
> I think the whole point is to make it annoying enough that it'll get
> fixed quickly. It can't be that bad or you'd have rolled a patch for
> it right? ;)
> 
> andrew
>