Referencing the different the relevant mautic versions

[fakela]

Referencing the different a d relevant mautic versions and important tips/requirements they need to know to use each release. I figured out that it will be best to separate these out into a different PR.

Fixes #251

[fakela]

Hi @RCheesley , here is the PR, this is far from finished :), I have to fix some suggestions by vale but I would love a review if grouping the releases this way is a good idea and if there is anything you would love to be added.

[RCheesley]

This is a great start - we could also perhaps include what features came in with the feature releases (e.g. 3.1, 3.2, 3.3) if that's easier to do with this setup. I like separating it out into the different files as it makes it much easier to reference and better for search engines.

Good luck pleasing the Vale gremlins, I found using VSCode with the Vale extension helped a lot as it shows you inline where there are failures, so you can pick it up much easier. Shout if you need any help, I had to use a couple of websites to get hints on how to change from passive to active voice, it's not easy!

[Victorybrown]

IMPORTANT: Please read our release blog post at https://www.mautic.org/blog/community/mautic-4-standing-tall, which contains important information about things that have changed in Mautic 4. Importantly you will need to make a one-line change to your theme configuration file.

Developers and advanced users: There is some important information about changes to configurations and plugins, which can be found in https://github.com/mautic/mautic/blob/features/UPGRADE-4.0.md

[Victorybrown]

I think this should be mentioned as well. takes you to the upgrade 4.0md

[RCheesley]

@fakela looks like we need to resolve a conflict and probably pull in the changes from main before we can look at taking this one further. I also agree we should include the link to the release notes & blog post for the 4.0 release :)