Open gregcorbett opened 2 years ago
It's probably better to tackle this in a bottom-up/iteratively fashion (i.e. how high can we upgrade doctrine before we need to upgrade another component first)
And many, smaller, pull requests are probably much better than big one that does everything.
we use composer 1, which is being deprecated in favor of compose 2.
Once https://github.com/GOCDB/gocdb/pull/509 and https://github.com/GOCDB/gocdb/pull/494 are merged, this can be ticked off as the composer files have been tested using and are supported by composer 2 (in fact, our environments are set up such to always use the very latest version of composer 2).
As an update on this - I see the next steps as:
Shortly after that, rebase and merge:
Sometime after those,
Once #509 and #494 are merged, this can be ticked off as the composer files have been tested using and are supported by composer 2 (in fact, our environments are set up such to always use the very latest version of composer 2).
Several parts of GOCDB are in need of a version uplift.
There is an core chunk of stuff around PHP, Composer and Doctrine.
It's probably better to tackle this in a bottom-up/iteratively fashion (i.e. how high can we upgrade doctrine before we need to upgrade another component first) rather than a "go for the head" of going straight to PHP8 and dealing with the fallout.
Other things to update