chore: update release process documentation

[gagik]

This uses the wording from the mongosh release process to better direct our process with Jira and publicizing our release.

[Copilot]

Pull Request Overview

This PR updates the release process documentation to align with MongoDB's standard release practices, incorporating Jira workflow management and communication requirements similar to mongosh.

Key Changes:

• Replaces automated workflow descriptions with step-by-step manual process
• Adds Jira ticket management requirements for releases
• Includes verification steps and Slack communication requirements

[coveralls]

Pull Request Test Coverage Report for Build 18869948188

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.002%) to 80.128%

---

Totals
Change from base Build 18847594160:	-0.002%
Covered Lines:	6303
Relevant Lines:	7727

---

💛 - Coveralls

[nirinchev]

I think we need to mention that we need to rename the vNext release in Jira, release it, then create a new vNext with start date today.

[nirinchev]

Not opposed to this but curious to hear what's the benefit of having a release ticket as opposed to just looking at the tickets linked to the vNext version?

[gagik]

biggest benefit is being able to track the release status & who did the release through Jira. Can be useful i.e. for external stakeholders to find the right person to contact or for them to block their release against ours.

[nirinchev]

Fair, but in that case, I'd suggest we need to have some automation that would generate the ticket. It sounds a bit tedious to link a bunch of tickets together.

[gagik]

I agree about automation

It sounds a bit tedious to link a bunch of tickets together.

To clarify, this release ticket is just a regular ticket tied to the release version so no extra linking needed.

[nirinchev]

Ah, I read the "correctly mapped" section from point 2 as we'd need to link them to the release ticket, not that we link the version from the release ticket and then look at the tickets for that version.