[Content] Create blog post to announce release of Mautic 5.2

[RCheesley]

In October we'll be making the Release Candidate release for Mautic 5.2. This precedes the General Availability by one month, and gives people time to test the upcoming release.

The release is called 'Pleiades' (pronounced 'Ply-a-dees') after the star constellation - our release themes are all based on constellations, with patch releases within them being stars from that constellation.

Our last releases have been Andromeda (5.1) and Alpheratz (5.1.1). Mirach (5.1.2) and Orion (6.0-alpha) will be released on the same day or maybe the following day.

Here you can see the announcement for 5.1: https://www.mautic.org/blog/community/release-announcement-mautic-5-1-andromeda-edition

Here's the announcements for 5.0: General Availability: https://www.mautic.org/blog/community/mautic-5-beyond-expectations-beyond-limits Release Candidate: https://www.mautic.org/blog/community/announcing-mautic-5-release-candidate Beta: https://www.mautic.org/blog/community/announcing-mautic-5-beta-now-available-testing

In order to find out what is being released in Mautic 5.2, you can review the merged PRs in the milestone here: https://github.com/mautic/mautic/pulls?q=is%3Amerged+is%3Apr+milestone%3A5.2+sort%3Aupdated-desc. Currently there are 160 merged PRs, it wouldn't surprise me if we got up to 200 by the time the release happens (this is a very large number for a release).

Feel free to ask in #t-product and/or in the PR itself if you aren't clear what the PR is doing, sometimes the title/descriptions are not so clear!

Please write the content in this Google Doc: https://docs.google.com/document/d/1yc5v-tg8RvCv9O5bdtuaYFp1cLpZ0kr70_20SrEWzcU/edit?usp=sharing.

Thanks!

[TusharGupta-Developer]

@RCheesley Hi, I would like to work on this issue. Could you please assign it to me? Thanks!

[RCheesley]

Hi @TusharGupta-Developer that would be awesome, thanks for being willing to help, so great to have you on board!

Hopefully you should have everything you need in the issue description. It's good to pull out marketer-facing and developer-facing changes because they are our two primary personas who care about what's in a release. This also helps the marketing team when preparing the visuals for the release.

Once the blog post is done, we can also draft the Release Notes, if you feel up to it.

GitHub generates some automatically but they are often badly worded using the title of the PR which isn't very helpful for users.

Here's how I organised it for the 5.1.0 release: https://github.com/mautic/mautic/releases/tag/5.1.0 but it was very basic, mostly I didn't change much in the titles because we left it to the last minute - I just sorted them into categories and used some emojis to denote the category.

The syntax to use for listing a PR is as follows:

* Autowire repositories by @biozshock in https://github.com/mautic/mautic/pull/13083

This ensures that the user is credited, etc.

Feel free to start with the blog post and as you go, perhaps make notes for what would become the release notes.

[Achi-edu]

Hi @TusharGupta-Developer, I'm just checking in to see how everything is going. Let us know if there is anything we can do to support you.

[RCheesley]

Due to the lack of response I'm going to open this task out to others.

[RCheesley]

Thanks @eddie477 for taking this on!

[eddie477]

Hey! No problem.