More chatty release bot

[TomasTomecek]

Since we closed the dedup issue, let's start a new one.

When something goes wrong, release-bot usually doesn't provide any details and we need to inspect its logs. It would be much better for the bot to be more social and rather speak about what went wrong. The biggest problem here, as pointed out by @jpopelka, is for the bot is not to produce duplicate messages.

Origin: #113 (comment)

[shahwan42]

Can I take this as part of my long-term GSoC participation?

first thing I see: we should let the maintainer know the important events like when a release was successful or not through the notification daemon or email?

[TomasTomecek]

when a release was successful

Release-bot already does this.

not through the notification daemon

I'm sorry but I don't know what this is.

email?

I'd personally prefer to use github comments and issues: emails are too hard.

[Aniket-Pradhan]

The notification daemon

It's a daemon used to send desktop notifications. It will be useful if you're running the bot on a personal desktop, and not on a container or openshift.

[TomasTomecek]

Oh, okay then. Feel free to send such support but TBH, I think most of the people would prefer to run the bot somewhere in the cloud and don't care about its management.

[shahwan42]

OK will start working on it right after my midterm exams