Drop support for Symfony <3 #306
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
should we make a release with all the existing changes before that ? |
stof
reviewed
Jun 4, 2019
|
I don't know. I initially wanted to merge / close as many issue as possible and then make a release. But IMHO, it's a bit stupid to do a release, and then to continue to merge new things... I would go for simplicity: do a release after merge of pending PRs (this one, the one about mailer, and a another couples) |
|
ping @symfony/deciders |
|
I agree, let's do one release with everything, including the bumps for the deps. |
lyrixx
added a commit
that referenced
this pull request
Jun 11, 2019
This PR was merged into the 3.x-dev branch. Discussion ---------- Drop support for Symfony <3 Commits ------- bca34c1 Drop support for Symfony <3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.