-
Notifications
You must be signed in to change notification settings - Fork 823
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
Set up next major branches for development #10349
Labels
Comments
maxime-rainville
changed the title
Clean up master branches
Set up next major branches for development
Jun 6, 2022
5 tasks
This was referenced Aug 2, 2022
This was referenced Aug 4, 2022
This was referenced Aug 9, 2022
This was referenced Aug 10, 2022
This was referenced Aug 17, 2022
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Blocked by - #10444 - the lack of support for using silverstripe/recipe-testing 3 as a proxy for saying "this unit has phpunit 9 support" causes the
LogicException: getItemPath returned null for SilverStripe\Dev\State\FixtureTestState. Try adding flush=1 to the test run.
issue in silverstripe/recipe-core and other builds. That PR removes the detection entirely so this issue should resolve itself once the PR is merged.Master branches are meant to be for the next major release. However they are in a pretty bad state right now and are way out of sync.
Now that CMS5 is back on the horizon, we need to re sync them.
Acceptance criteria
master
.Notes
Some more PRs
Other PRs
PRs
Remove branch-alias from master
The text was updated successfully, but these errors were encountered: