> Hi, > > That's a bad thing we need to fix ASAP. > > I think for 5.6.1 we'll revert it , if not, we'll need an RC2, which > is something we usually don't do (but as this could involve security, > we may do it). > The fix can be merged to 5.5.18RC1, next week, to have an RC cycle if > not part of a 5.6.1RC2 (tag is tomorrow) > > 5.6 and 5.5 actually overlap in the release weeks. 5.6 is planned on > odd weeks whereas 5.5 is on even weeks. > > Waiting for Ferenc's advice anyway. > > Julien.P
I have no issues with reverting at this point as that's the best route to get stable releases back on track. I thought I had fixed some really old bugs with those commits but the medicine turned out to be worse than the disease. My apologies again for letting those problems sneak into releases :/
