-
Notifications
You must be signed in to change notification settings - Fork 2
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
Create CMS 6 branches for all commercially supported modules #191
Labels
Comments
This was referenced Feb 19, 2024
This was referenced Feb 19, 2024
Reassigning to Steve since there's still a PR in draft |
This was referenced Feb 20, 2024
Assigning back to Steve for ci or whatever else is needed next |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's time! We're ready to open some branches in preparation for CMS 6 work.
Acceptance criteria
- CI for all commercially supported modules passes on the next major branch for all commercially supported modules- CI for the next-major branch does not run on a cron- Merged ups still between 5 and 6 are enabled.Things we are explicitly not doing yet
6
to the docs dropdownaffects/v6
label? (i.e. if we see a bug that only happens on the new6
branch, it should be labelled withaffects/v6
)Other concerns
We'll have a seperate card to handle Rhino updates.
New issues created
Tool used to create PRs
PRs
Updated PRs
The text was updated successfully, but these errors were encountered: