Update the Release management process guidelines

I recently sent an email about switching from backport-based release management to 'forward-port' (whatever that actually means), where we merge release branches into master instead of cherry-picking the opposite way.

We need to have the guidelines updated on this.

[NicolasT]

like ;-)

💛

[JordanP]

Now the real question here is: should we call this "port" or "forward port" ? I can't sleep !

[NicolasT]

'Reverse-backport'?

Don't start me on a stupid naming scheme, I might be able to find some ludicrous ones.