Clarifying branching and versioning in RELEASE doc

[mjurc]

Summary

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[fedinskiy]

Thank you!

[fedinskiy]

The format is ok, this is a documentation only change, so there is no need to wait for code CI