User tests: Successful: Unsuccessful:
Seriously?
Openness fail
"please user 45 differents tools before submiting some fix to our apps, 'cause time wasted to patch our code is not enough. Cheers" #sarcasm
I'm not a Joomla expert, but testing this might prove a tad difficult...
I don't what it has to do with openness since the process and the fact that the tracker not git hub is the point of truth for issues is documented in a million places. The way you test manually is to apply it and make sure that nothing changes, which obviously will be true in this case since this is just a code quality fix. Also the pull would need to be revised since it includes a platform change unless you've sent that change already to the platform repo.
PHP.
I would say that THIS is the right case to choose pragmatism over process...
rly? lol!
It would be really helpful if you could submit the fix for libraries/joomla/database/driver/pdo.php to joomla/joomla-platform. We treat the platform like an upstream library and we'll pick up the fix with the next merge. The platform accepts pull requests BTW ;)
@pborreli
Thanks. I added tiny comment, just waiting for the unit tests to pass (http://developer.joomla.org/pulls/) and I'll merge it.
Please create a tracker on joomlacode, reference here and explain the issue with testing instructions.