Swap deploystacks for OPT_IN_TEST_NEXT_MINOR and OPT_IN_TEST_NEXT_MAJOR
Closes #3456091
Merge request reports
Activity
added 1 commit
- 21dfc432 - Fix core_version_requirement so NEXT_MAJOR runs
Had a thought about this today and this is what I think we'll go with.
The existing deploystack/matrix stuff for Gitlab is a bit yuck. Im not super happy about the way gitlab_templates puts together is "matrix" -alike. But we'll give it a shot.
For the 2.6 series, I'm repurposing it for ^10.2 and PHP 8.2. 10.3 and 11 is being pushed to the next series. The 2.6 branch will already have potentially disruptive changes, per 49bf5b4f, and the Messenger set of changes. So I'm going to isolate it from core changes, as thats what I'm comfortable with. That of course doesnt prevent a 2.7 series from being developed simultaneously. I'll resurrect the next-major and constraints there.
Edited by dpiadded 2 commits
mentioned in merge request !45 (merged)