-
Notifications
You must be signed in to change notification settings - Fork 71
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
Support Sylius 1.7 again #230
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @Zales0123
It's great, and I thank you for that 🚀
I put minor comments, but this PR can be merged without if needed.
On off-topic note, I hope stable release won't be done until architectural problems are solve as discusses in #193 |
44d7d65
to
1cb2604
Compare
1cb2604
to
b6b62e0
Compare
Hi, PayPlug team here 👋 We are working closely with Synolia in order to release our first Sylius x PayPlug plugin, we are pretty excited to make it happen! 🚀 I have two questions for you:
Thanks ! |
Thanks, Mateusz! 🥇 |
Hi @alopez-pp! Thank you for your kind message :) As the PR is merged we will release the next tag Regarding the second question. Sylius 1.7 is already not actively maintained for the last 2 weeks, it will get only security fixes for the next months. It's highly recommended to everyone to upgrade to the latest supported 1.8 and, as creators of both Sylius and this plugin, we need to bump to supported releases as fast as possible. I think you understand our perspective 🖖 If you have any more questions, I would be glad to answer them 🚀 |
This PR was merged into the 1.0-dev branch. Discussion ---------- Associated with #230 As Sylius 1.7 is already not actively maintained, we need to bump to supported releases as fast as possible and we would like to encourage everyone to upgrade to the latest supported version: Sylius 1.8. All opinions are appreciated 😃 Commits ------- 523da79 [Maintenance] Drop Sylius 1.7 support
With the latest
v1.0.0-RC.4
, we've introduced support for Doctrine Migrations 3.0. However, it required from us also to support only Sylius ^1.8... with the support for Sylius ^1.5 in the previous tag.I believe it was a mistake. Doing such a big and work-demanding change as migrations version switch together with bumping Sylius requirement by 3 versions can be a pain in the back for a lot of developers using
RefundPlugin
already.I think that doing a step backward can improve the developer experience for those, who already use this plugin. Definitely, the next release (hopefully the stable one already 🤞) would support Sylius 1.8 only, so this one is just an intermediate stage. The implementation is not perfect as well but allows us to test 2 versions of Sylius along with 2 versions of PHP and MySQL 💃
I would love to see your opinion 🖖