Document a better release process

[Pierre-Sassoulas]

Type of Changes

	Type
✓	✨ New feature
✓	🔨 Refactoring
✓	📜 Docs

Description

Follow-up to #5877. This document the new git flow, based on review for pylint-dev/astroid#1438

Closes #4701

[DanielNoord]

Haven't looked yet but two shower thoughts:

1. We should probably split the Copyright change into its own PR and commit, that's not really part of the release process
2. Not sure if you thought about this, but: we should probably remove the requirement that allows the dev version of astroid from the commit that is made into a release. That way user's will get warned when they install dev astroid + stable pylint. Process would be something like: 1. Update version and requirements to remove dev marker, 2. Update version and requirements to add dev marker.

[Pierre-Sassoulas]

We should probably split the Copyright change into its own PR and commit, that's not really part of the release process

Yes there is 3 different things here, I've been lazy :) I'm going to open other PR.

[Pierre-Sassoulas]

Blocked because we're going to merge the PR in astroid first and do the same change here after that.

[coveralls]

Pull Request Test Coverage Report for Build 1950576288

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 94.005%

---

Totals
Change from base Build 1948147488:	0.0%
Covered Lines:	14944
Relevant Lines:	15897

---

💛 - Coveralls

[DanielNoord]

@Pierre-Sassoulas To make this a little easier, shall we just copy the one from astroid? I don't think there is that much that is specific to astroid right?

[Pierre-Sassoulas]

Yes, I'm going to do that :) I'm doing #5877 first and catching up with other MR

[Pierre-Sassoulas]

@DanielNoord this is the same process than in astroid with the following modification : aa51220