Closed joshdavies14 closed 2 years ago
@skiros8732 Ik previously we had spoken about changing how the calls to the SU api work, moving it to when someone tries to sign in with their ITS account as opposed to checking every 5 minutes whether anyone new has joined the society. I don't know what future web plans are, but I suppose the questions are as follows:
If we would like to make changes, doing it alongside the Wagtail upgrade is probably an ideal time to do so IMO.
We are currently on 2.15, the current LTS version of Wagtail, and the new LTS version (supposedly 4.1) is slated for public release 1/11/22. There will be a few release candidates before this version is officially released, hopefully these will be available come early-mid October.
Once the first RC arrives, we should take the opportunity to go through every dependency we have on Dextre and update where necessary, or remove it if it isn't actively being used by the website. We'll also hopefully include an update to Django 4.X in this upgrade (our current version of Wagtail only supports up to 3.2, which is what we are on) - at the same time, 3.2 is the latest LTS version and will be the LTS version at the time of upgrade.
The upgrade will take place version by version, so currently 2.15 -> 2.16 -> 3.0 -> 4.0 -> 4.1, ensuring any upgrade considerations are taken into account at each stage. Testing will take place locally, but the staging environment will also be used to ensure the upgrade goes as smoothly as possible.
It's worth considering if there are any major features people want implemented at this time, as this will be a big upgrade, the process will be longer to begin with, so if anything wants doing, now is the time!
See #22 for last year's upgrade.
Useful reference links: Upgrading information: https://docs.wagtail.org/en/latest/releases/upgrading.html 4.1 release notes: https://docs.wagtail.org/en/latest/releases/4.1.html