Re: DBD::mysql path forward

Pali,

I have given you co-maintainership to DBD::mysql and permissions on the 
repo - let's go ahead and move forward.

Thank you,

Patrick

On 11/3/17 11:17 AM, Patrick M. Galbraith wrote:
>
> Pali,
>
> Sorry, I wanted to give it time for people, plus have been very busy. 
> I'm ready, just let me know when we can get code merged back in-- what 
> do you need me to do? I will need help with this.
>
> Regards,
>
> Patrick
>
> On 11/2/17 1:43 PM, [email protected] wrote:
>> On Tuesday 12 September 2017 11:40:31 Patrick M. Galbraith wrote:
>>> Hi all,
>>>
>>> After talking to Pali and looking at how other drivers have handled
>>> the issue, the best way forward will be to deal with solving the
>>> UTF-8 issue correctly as was attempted in May. This will be a
>>> problem for some, but only due to having to been accustomed to a
>>> work-around that relies on a intermittent and buggy implementation.
>>> The plan is to give ample time to let people prepare and comment as
>>> well as give them a chance to try the changes and adjust prior to
>>> stable release. I'm going to look through the mailing list and find
>>> particularly those who had problems back in May and June when we
>>> tried this before and work with them in advance of the change.
>>>
>>> DBD::mysql should be on par with all the other DBD drivers and allow
>>> transparent usage regardless of backing RDBMS, and this really is the
>>> only way. It will also allow for other fixes to proceed and the
>>> driver to continue improving and supporting all versions and
>>> enhancements of MySQL and MariaDB.
>>>
>>> Please do give us your thoughts on this as we want to be as helpful
>>> and transparent as possible.
>>>
>>> Thank you!
>>>
>>> Patrick
>> Hi! Nearly another two months passed and there is no progress in
>> unblocking development.
>>
>> Currently more people started reporting problems that new versions of
>> both MySQL and MariaDB cannot be used for building DBD::mysql.
>>
>> As I stated two months ago, we are thinking about forking DBD::mysql as
>> inability to build DBD::mysql with new version of MySQL or MariaDB is a
>> real problem which needs to be fixed ASAP -- and not waiting another 6
>> months.