chore(maintenance): update release flow diagram

[dreamorosi]

Description of your changes

This PR updates the content of the diagram that shows the release process in the maintainers handbook.

Before

After

Related issues, RFCs

Issue number: #2044

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[am29d]

Thanks for detailed update on the visualisation. I was wondering if we should add manual PRs visually and the separation between version bump and release workflow. What do you think?

[dreamorosi]

Hi, thanks for the review!

I have update the diagram to make the manual steps stand out more (converted them into milestones):

Regarding the separation of version & release I would leave it as a single section/diagram. I have however updated the description above to more explicitly call out that the release process is composed by multiple district workflows.

[am29d]

Nice! Thanks for the update, now it's much better.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud