-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
🥔 Should we keep rebasing 3.0? #7379
Comments
As discussed in chat, this is currently problematic: we'll most likely need to consider all branches under a certain naming convention (such as |
We now have 151 PRs targeting I'm pretty sure most of the 151 are already outdated and need to be rebased, but even thought that's the situation I think we should strive to consider With the current state of the repo, it's way easier to port a bugfix forward to |
On top of what @lcobucci said, I'd also like to mention that 2.6 vs master is not just a few commits and changed files, but a lot of fundamental changes and completely overhauled coding style. |
Internal question for discussion group. |
@doctrine/doctrinecore Feel free to vote.
👍 For "Yes, continue"
👎 For "Stop, let's choose another alternative (ie. merge, cherry-pick)"
The text was updated successfully, but these errors were encountered: