-
Notifications
You must be signed in to change notification settings - Fork 114
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
Release more frequently #59
Comments
These PR are features, so we can easily image a 1.2.0 now and a 1.3.0 with the #21 ^^ |
We want to integrate #21 before tagging a new major release. There were a bunch of changes in-between which will require that we release it as We'll show more diligence in the future. :-) Our next major focus is going to be full Symfony 4.3 support. |
Is there breaking changes? Thank you and good luck! :) |
We are aware that there hasn't been a new release in a while and we will definitively try to be better in that regard in the future. Just a bit of a background though - first there was a breaking change in We'll have to tag the new release as 2.0 as there have been some breaking changes that happened on the |
May I suggest to release a 2.0.0-alpha1 for us early adopters? We can release that now so people can test and find bugs. |
There is no tagged release since 1.1.0 in January 2019 and master is ~90 commits ahead with lot of new things.
Consider tag and publish more frequently to help up keep our
composer.json
clean (nodev-master
) and a easier way to check changes through time.Thank you for your work :)
The text was updated successfully, but these errors were encountered: