-
Notifications
You must be signed in to change notification settings - Fork 29
Are we ready to Symfony 3.0 ? #220
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
Hi @ksn135, Our first priority would be to make a stable release of this bundle, with all correct documentation in place. Actually, I was planning to start on the documentation this holiday break. It is actually a reboot of #75, but that doesn't matter. I would also like to close as much issues as possible before making the bundle Symfony 3.0 compliant. Another thing that I worry about is the minimal PHP version: currently my development is on PHP 5.4, which does not support the Therefor: first fix as many bugs as possible here and create a decent documentation, tag that as stable for Symfony 2.x and then start on the Symfony 3.x branch. |
Well, I could help in closing tickets, but I'm not native English speaker so I can't help with docs.. ( |
In PR #221 I removed as much as possible deprecated calls I've seen. My plan is to finish this PR, then create a new one bumping the Symfony version to 2.8 and remove deprecations. Let me know if it makes sense for you, |
@sescandell good plan |
Yes we are! Well... once #224 is merged ;) |
Hi there, everyone!
May be we should make a new branch ?
What do you think about it ? Let's discuss it!
More?
The text was updated successfully, but these errors were encountered: