This PR can't be tested/reviewed/acted upon until a proper 4.0 project has started somewhere. Also this PR can't be considered for 3.x since it raises minimum PHP dependencies. My suggestion is to close this until there's a proper 4.0 branch/project somewhere then this PR be opened against that.

// @wilsonge

Raising the PHP requirements is already in the pipeline.
So, instead of closing this, opening a 4.0-dev branch makes more sense to me.

You'd still have to close & re-open the PR against that branch unless whomever is maintaining it will manually cherry-pick this PR onto it or GitHub finally added the feature that lets you change a PR's target branch.

I'm just trying to save time for folks looking at PRs right now so they aren't looking at or commenting on stuff that isn't applicable.

Ah ok, got you.

We really want to try and not turn the issue tracker into a to-do list

Whatever space Joomla 4 ever ends up living in is either going to have a GitHub issue log full of todo tasks or require an external resource as a project management board for items like that. It's not something that can be avoided unfortunately.

@rdeutz As this is your team's area if this is something we want to work on IMO we probably should come up with a migration plan.

A proper plan would be great, maybe we can sit together at JAB17, closing it for now.