To be fair, if they were going to do this, they wouldn't have invested the thousands of hours required to release 5.6, 5.7, Fabric, the mysql toolkit, etc. I've talked to the developers in person who work on MySQL, and they talk quite a bit about the future of MySQL.
They have also acquired a number of MySQL based companies, and are committed to supporting them on MySQL.
A better strategy is the one they currently use - selling support tools (like Enterprise Support, Enterprise Monitor, and Enterprise Backup) to support the development. It never ceases to amaze me how much people will pay for these tools and services to support a OSS product.
I'm guessing there is a sizable slice of applications that would find PostgreSQL to be "good enough", and not need to buy Oracle subsequently.
Perhaps that's just paranoid, and Oracle is running MySQL out of the goodness of its corporate heart?
Based on personal experience, when databases hit that point, the logical next step is PostgreSQL if you're going to go through the pain of changing database engines. Or just do what $oldjob did and throw more and more resources at MySQL (256GB memory, anyone?).
* Slightly better performance IIRC
* Not controlled by Oracle, who will likely kill off MySQL to promote their own database at some point in the not-too-distant future.