On Tue, Sep 12, 2017 at 11:54 AM, Dan Book <gri...@gmail.com> wrote: > On Tue, Sep 12, 2017 at 11:04 AM, Patrick M. Galbraith <p...@patg.net> > wrote: > >> Pali, >> >> Yes, I agree, we'll have to create a fork pre revert and stop accepting >> PRs >> >> How might we allow people time to test the fixes to give them time? Just >> have them use the fork, I would assume? >> >> Regards, >> >> Patrick >> > > To be clear, this sounds like a branch not a fork. If your plan is to > reinstate the mysql_enable_utf8 behavior as in 4.042 rather than adding a > new option for this behavior, then branching from 4.042 seems reasonable to > me; but you should be very clear if this is your intended approach, as this > is what led to many people corrupting data as they send blobs to mysql with > the same mysql_enable_utf8 option, and expect them to accidentally not get > encoded. > > -Dan >
And one other note, if you do reinstate the 4.042 behavior, due to the backcompat breakage at the very least this should be a 5.0 release. -Dan
