It's time! We're ready to open some branches in preparation for CMS 6 work.
Acceptance criteria
All commercially supported modules have a next-major branch
Composer dependency constraints point to the new branches
Update - the following have been split off on this new card- 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
Changing default branches
Adding 6 to the docs dropdown
Adding affects/v6 label? (i.e. if we see a bug that only happens on the new 6 branch, it should be labelled with affects/v6)
Other concerns
We'll have a seperate card to handle Rhino updates.
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