-
Notifications
You must be signed in to change notification settings - Fork 684
mySQL 5.7 support roadmap #178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think this might be a case of the README being outdated? We're running all of the tests in 5.7 on travis successfully. |
awesome, thanks for the quick response! |
You can open a PR for the README ;)
Le jeu. 8 déc. 2016 à 20:26, Matthew Schmohl <[email protected]> a
écrit :
… awesome, thanks for the quick response!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#178 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAVFXReHloVdJoS7dIn1sdFEr6vNmfJlks5rGFnMgaJpZM4LILYD>
.
|
kdparker
added a commit
to kdparker/python-mysql-replication
that referenced
this issue
Dec 8, 2016
baloo
pushed a commit
that referenced
this issue
Dec 9, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi all,
Thanks again for the great project. Since I've seen some rumblings of 5.7 support, I was wondering if any documentation could be exposed w.r.t. a roadmap / which feature branches are supported / known limitations. Thanks inadvance!
The text was updated successfully, but these errors were encountered: