-
Notifications
You must be signed in to change notification settings - Fork 183
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
Symfony 4 / v2 / is this bundle obsolete? #332
Comments
yes? no? maybe? is this project dead? |
Just bumping this thread, it would be really nice to have a stable release that includes Symfony 4 support. |
@MrQuery @Gadgetdude projects not quite dead yet, I've been handed the reigns and it's something I now have time to work on I'll add the release tag later on this week, want to do some testing on the current state of the project first |
righty, I've tidied the issue chain and I'll be doing some updates when I have time |
testing complete on 4.0, see #334 for unit/functional/all test results aiming to have latest complete today (if possible) |
moving on to latest version, created documentation on gist for getting setup quickly from what I've just done with 4.0 should work with latest, will update shortly https://gist.github.com/hex333ham/9fae56fd8f0cdf26f7377a150dc9d72a |
4.1 is fine and those instructions work, for details on automated test results see here - #334 |
|
nevermind, I forgot a few things (need more coffee), deleting that release |
alright, never try the easy route (edit in place, bad practice anyway), creating a specific branch for 1.4 to fix deprecation errors - https://github.com/FriendsOfSymfony/FOSMessageBundle/tree/1.4 |
this is being moved to version 2.0 as I'm going to drop support for Symfony 2 (I can't actually get travis to successfully test on the lowest possible) see here for when it's going to be deprecated officially by symfony - https://symfony.com/roadmap/2.8 I'll add a note in the docs to use 1.3 if using Symfony2 |
build is passing when removing symfony 2.8 - #339
resolved issue with phpunit, but a new one pops up (due to the future deprecation of going to remove 1.4 branch when 2.0 is released (going to give a couple of days to let people have "objections") |
I see no objections, merging to master |
merged to master, accidentally created the release (prematurely) so apologies for any notifications occurred from that I'm now going to close this issue and open a new one for the packagist thing |
hi,
how about tagging a new release version?
The v1.3 is about 2 years old and the master 3 months and has the symfony 4 support.
The text was updated successfully, but these errors were encountered: