Not sure what the official answer is, but I would think it would be along the lines of:
1) Write a patch to fix the broken code 2) Write a patch for the relevant test, adding a test case if there isn't one.. (Or maybe a test case referencing the ticket number?) 3) Attach to the issue Maybe after that sending the list a message would be good to draw attention to it. On Mon, May 18, 2009 at 3:20 PM, till <[email protected]> wrote: > On Mon, May 18, 2009 at 8:12 PM, keith Pope <[email protected]> wrote: >> Write a patch, this way you can re-patch the files if there is another >> release. Plus you can upload the patch to the ticket and hope it will >> get applied :) > > We pretty much do the same that Keith suggested. That's the last > resort though, if possible we extend classes and avoid patching. You > could also use runkit to monkey patch PHP code. ;-) But that's > probably not wise in production. > > Till > -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
