You may want to take a look at this:

Am 11.01.2017 20:23, schrieb Thomas Bruederli:

Dear subscribers, we wish you all a happy new year!

Today we published the beta release of the next major version 1.3 of
Roundcube webmail.

[..]

We're keen to hear your feedback about the new release.

Best,
Thomas & Alec

If feedback is requested for a specific version, I have to use this version,
right? If I shall not use it, then I can't give any feedback.

They tagged a version for that, https://github.com/roundcube/roundcubemail/tree/1.3-beta

Am 07.02.2017 13:31, schrieb cor@xs4all.nl:

If you insist, at your own perit, in using a development branch, then please
keep any reports constructive.

How more constructive than "completely broken/unusable" can I be if that is
the case...? It's simply dysfunctional, can't access almost anything.

And there are still reasons why to use 1.3-beta, as in the so-called
"stable" version some things do still not work which do/did work in the beta
for a long time already.

There is a difference between a tagged beta, and git master. Git master may get ‘completely broken/unusable’ code pushed, for instance because they want to save work in progress and dont want to risk losing it when their laptop gets stolen. Whatever, there may be all kinds of reasons.

I found your comments a bit aggressive. Words like "completely broken/unusable”, “Please test your stuff before committing”, "Urgent fix appreciated”. Nothing about git-master is urgent. It is the current head of the development branch and should be treated as very risky. Now, you’re more than welcome to run it, but then accept the fact that it may be broken at times. That’s the nature of the beast.