Skip to content
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

Open
dkisselev opened this issue Nov 14, 2015 · 6 comments
Open

A new dot-release? #396

dkisselev opened this issue Nov 14, 2015 · 6 comments
Assignees

Comments

@dkisselev
Copy link
Contributor

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.

@jief
Copy link

jief commented Nov 15, 2015

+1

@florianeckerstorfer
Copy link
Member

I will try to get a release out this week. Does the develop branch currently works fine for you?

@florianeckerstorfer florianeckerstorfer self-assigned this Nov 23, 2015
@althaus
Copy link
Contributor

althaus commented Nov 27, 2015

@florianeckerstorfer Just updated to latest version and it runs fine for us.

@dimkir
Copy link

dimkir commented Dec 9, 2015

+1

@dkisselev
Copy link
Contributor Author

@florianeckerstorfer I've upgraded to a develop release and have not encountered any issues, along with the new integration tests and @althaus's account of it working looks like the bundle is pretty good to go overall.

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.

dkisselev referenced this issue Dec 23, 2015
Previous methods have been deprecated as of Twig 1.28 and Symfony 2.7+ triggers
deprecation errors
@robertfausk
Copy link

Any news here? There are a lot more commits since december last year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants