Rocket Chat has a lot of problems (LTS branch needed)


Hiya Rocket Chat Community!
First off, I want to start out saying amazing work on getting this piece of software together. Based on many search attempts, I don’t think there is any good alternative open source chat system such as this. However … We have some problems :frowning:

One of the biggest things that has kept me away from using Rocket Chat beyond a testing environment is the sheer amount of issues/bugs it seems to possess ultimately making it unstable for long-term production use. Yet, I am noticing the community seems to still be quite focused on Implementing new features ATM.

One thing I’d love to see happen is a release with focuses solely on stablising the current code so it’s truly production ready. Compared to alternative OSP, nothing comes close to the features which are already here, but aren’t very stable. By focusing on fixing what is here now, Rocket Chat can truly become a competitor to the likes of Slack, Microsoft Teams, Discord, etc. But as it stands, the walled gardens are the more likely choices due this huge flaw of instability.

One user suggested implementing a LTS branch, which I think would be the best way to tackle these issues while still working toward new features. I personally think this would be the best approach overall for the long run.


A LTS version of course has a certain appeal and makes sense in certain environments. The question is whether this is the case with, as the project is clearly in flux and is being developed very actively. We’ve been running Rocket.Chat productively for more than two years and I can’t say that the installation has let us down even once. So I think that Rocket.Chat can be used and recommended in a productive environment with a clear conscience. Regarding possible bugs it helps to report them on github. From my own experience I can say that all bugs I posted there were fixed when a clean issue was posted. This is an agility that I really appreciate and I wouldn’t want to be nailed to a version for five years like Ubuntu Server LTS. There’s still too much going on in this segment for that. And separate maintained version branches are more time-consuming. The question is whether it’s better to bundle resources on a rolling versioning. Updates have to be installed anyway, whether LTS or not.