Requests for comment/Release notes automation

Introduction
Most of the devs have encountered a merge conflict due to RELEASE-NOTES. This RFC proposes a bot to monitor master merges, and automatically append text based on the commit's message magic keywords. The bot doesn't have to handle all complex scenarios - in case of a problem, someone could do a regular file patch as it is done now.

Commit Message Magic
RELEASE Bug fixes plus some text with a space in the front
 * some long text

This line will not be added because it does not start with a * or a space. Blank lines are ignored.

RELEASE Languages updated
 * some more text will go into a different section.


 * All of that text will be automagically added to the RELEASE-NOTES sections once the bot detects that a branch has been merged with the master
 * It would be ideal if the bot checks if such header actually exists in the file and emails user in case of an error (on branch commit, not on merge)
 * It would be great if Jenkins detected those errors
 * Bot should understand any of these forms of headers:

RELEASE === Bug fixes === RELEASE === Bug fixes in 1.21 === RELEASE Bug fixes RELEASE Bug fixes in 1.21