Skip to content
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

The Great Upgrade #337

Open
1 of 4 tasks
gregcorbett opened this issue Feb 17, 2022 · 4 comments
Open
1 of 4 tasks

The Great Upgrade #337

gregcorbett opened this issue Feb 17, 2022 · 4 comments

Comments

@gregcorbett
Copy link
Member

gregcorbett commented Feb 17, 2022

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

@gregcorbett
Copy link
Member Author

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.

@gregcorbett
Copy link
Member Author

gregcorbett commented Mar 20, 2024

we use composer 1, which is being deprecated in favor of compose 2.

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).

@gregcorbett
Copy link
Member Author

gregcorbett commented Apr 22, 2024

As an update on this - I see the next steps as:

  1. Drop PHP 5.4 support: Drop PHP 5.X support #494 - after 1st July 2024

Shortly after that, rebase and merge:

  1. Unit test against more versions of MariaDB: Unit test against newer versions of MariaDB #511
  2. Update ORM to 2.11 (or as high as we can go above that, maybe even 3): Update ORM to 2.11 #455

Sometime after those,

  1. Add support for PHP 8+: Add support for PHP 8 #513.

@gregcorbett
Copy link
Member Author

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).

#509 and #494 are now merged!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant