Re: DBD::mysql next steps

Hi Pali! On Thu, Nov 16, 2017 at 12:49 PM, wrote: > Hi! And what are you going to do with all commits which you reverted in > 4.043 version? As I remember, months ago you wrote that you reapply > fixes, but nothing happened. Instead you started merging conflicting > new pull

Re: DBD::mysql next steps

On Friday 10 November 2017 10:13:55 Patrick M. Galbraith wrote: > Greetings all! > > Michiel and I have been talking, weighing options of what course to take in > dealing with moving forward-- with the goal of both offering both stability > and the choice to have the latest functionality and bug

Re: DBD::mysql next steps

And I would suggest to disable issue tracker on github as primary bug tracker (according to DBD::mysql documentation) is on RT and also probably all problems are reported there. The worst thing which can be is to have two independent bug trackers, which is current situation.

Re: DBD::mysql next steps

On Friday 10 November 2017 10:13:55 Patrick M. Galbraith wrote: > Greetings all! > > Michiel and I have been talking, weighing options of what course to take in > dealing with moving forward-- with the goal of both offering both stability > and the choice to have the latest functionality and bug

Re: DBD::mysql next steps

Darren, Yes, the other plan definitely had its merits. Credit due to Michiel on that plan who really helped lay it out and explain the pros and cons of each and helped me to get that idea out. Kind Regards, Patrick On 11/10/17 12:24 PM, Darren Duncan wrote: I agree in principle with

Re: DBD::mysql next steps

I agree in principle with Patrick's plan. My strong recommendation for continuing development under a different module name was based on the assumption (but not the knowledge) that the Unicode/Blob problems were rooted in the DBD::mysql codebase in such a way that they blocked the ability to