Upgrade to Silverstripe 5

[wilr]

Description

Upgrade to Silverstripe 5

Manual testing steps

Issues

• tijsverkoyen/akismet constraint is too strict and might not work on PHP8 #44
• Required dependency tijsverkoyen/akismet is abandoned #39

Pull request checklist

• The target branch is correct
  • See picking the right version
• All commits are relevant to the purpose of the PR (e.g. no debug statements, unrelated refactoring, or arbitrary linting)
  • Small amounts of additional linting are usually okay, but if it makes it hard to concentrate on the relevant changes, ask for the unrelated changes to be reverted, and submitted as a separate PR.
• The commit messages follow our commit message guidelines
• The PR follows our contribution guidelines
• Code changes follow our coding conventions
• This change is covered with tests (or tests aren't necessary for this change)
• Any relevant User Help/Developer documentation is updated; for impactful changes, information is added to the changelog for the intended release
• CI is green

[wilr]

Note if Silverstripe limited no longer wishes to support the module as per the readme I'm happy to transfer to my handle as it is still one of our used modules. Or I can remove the notice now.

[GuySartorelli]

Hiya,
Sorry it's taken so long to comment on this.

The 4 branch is still supported for security fixes only, and we've committed to not doing any non-security patches on this branch.

That said, we don't have any commercial support for this module for CMS 5. If you'd like to maintain this module going forward, we'd be happy for you to do so, starting from a new major release on a new 5 branch. You should already have maintainer access as a core committer.