-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Could we have a tagged release with the Symfony 2.7 fixes please? #1844
Comments
+1 I just hit this bug upgrading - it's a stopper :/. But, kudos to already having it fixed :). |
Btw if anyone else wants to temporarily use the latest from master with the fix (bit riskier generally), you can ask Composer for it with:
Took me a few mins to realise! |
I've tagged a 1.3.6 release, but given the alpha state of 2.0, I will leave the release of that to @stof. |
That's great - thanks! |
I've added an extra pr needed for 1.3.x, see #1852 |
The seconds alpha is now available https://github.com/FriendsOfSymfony/FOSUserBundle/releases/tag/v2.0.0-alpha2 |
@XWB please don't make a release where unreviewed PRs are merged in it. Ask for review first. Otherwise it makes it very bad for people upgrading to such versions if we need to revert things |
Currently if you have either v1.3.5 or the latest tagged v2 alpha you hit issue #1775 - which completely breaks everything on the now-stable Symfony 2.7.
Would it be worth making some new tags, as the bug's already fixed in both branches' masters?
The text was updated successfully, but these errors were encountered: