Skip to content
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

Closed
3 tasks done
maxime-rainville opened this issue Jun 5, 2022 · 2 comments
Closed
3 tasks done

Set up next major branches for development #10349

maxime-rainville opened this issue Jun 5, 2022 · 2 comments

Comments

@maxime-rainville
Copy link
Contributor

maxime-rainville commented Jun 5, 2022

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

  • New major release branches are created on all the core modules. They use number formats instead of master.
  • The CMS5 installer is in an installable state.
  • Builds are running for the next major branches.

Notes

  • Maybe wait until GitHub Actions is used across all modules.
  • Don't delete the current master branches.

Some more PRs

Other PRs

PRs

Remove branch-alias from master

@maxime-rainville maxime-rainville changed the title Clean up master branches Set up next major branches for development Jun 6, 2022
@emteknetnz emteknetnz self-assigned this Jul 20, 2022
@emteknetnz emteknetnz removed their assignment Aug 18, 2022
@emteknetnz emteknetnz removed their assignment Aug 23, 2022
@emteknetnz emteknetnz removed their assignment Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants