Looks like we'll need a 5.7.0.CR2 to make sure we get such things right. Other open issues are also more invasive than expected, so I expected one anyway.

I'm not concerned with breaking APIs with development releases, like the previous 5.7.x. The backwards compatibility "promise" should apply to people migrating from 5.6 to 5.7.

When you mention "even in our tests, this translates into more than 90 compilation errors" that's not comparing to 5.6 codebase right? Or are we potentially breaking code of pre-generic Query usage as well?

I see no big value in adding a createTypedFullTextQuery at this stage; we can consider such things for 5.8 .. but as you say, it might be short-lived, unless we want to already flesh out the "right one", which will then become the only one in 6+. That would be ideal, and somewhat help the users eventually migrate to 6.