-
Notifications
You must be signed in to change notification settings - Fork 180
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
A new dot-release? #396
Comments
+1 |
I will try to get a release out this week. Does the |
@florianeckerstorfer Just updated to latest version and it runs fine for us. |
+1 |
Based on the discussion in #408, it sounds like there are a few more deprecations that came up. It would probably be best to wait until those are fixed so we can be 3.0 compatible right away. Hopefully we see some PR's and more testing to confirm that everything is covered soon. |
Previous methods have been deprecated as of Twig 1.28 and Symfony 2.7+ triggers deprecation errors
Any news here? There are a lot more commits since december last year. |
I would like to avoid using dev-master (or specifying an exact commit) in my composer.json, but there have been quite a few fixes since the last release in March.
@florianeckerstorfer it seems like you're pretty busy and can't actively work on the bundle, but would you be able to push out a 2.1.3 release so we can make use of those fixes in the mean time? (the Symfony 2.8/3.0 deprecations are the ones I'm most concerned about)
Let me know if there's anything in particular that you would like to see done before you can push an update, I might be able to help out with some PR's to get us there.
The text was updated successfully, but these errors were encountered: