However, a year later, their SaaS has been discontinued. The open-source repository is now stagnant, with hundreds of unresolved merge requests. On a positive note, they recently shared the repository with some other open-source maintainers, so there's hope that Redash will be reborn.
> On a positive note, they recently shared the repository with some other open-source maintainers, so there's hope that Redash will be reborn.
Yeah, the root of the problem (in my opinion) was that Redash has sooo many Python dependencies (due to supporting so many databases and similar) that it's become a real hairball source code wise to keep them all playing together nicely.
Especially as over time (say) library package FOO has some security vulnerability reported that gets fixed in a new release... but the dependencies of the newer release are too new to work with (say) package BAR. Times that by 50 and it's a real pita.
Simultaneously to that, the Redash team got busy with their work at Databricks (mostly not Redash related). Then the automatic CircleCI checks on PRs started failing (ugh), etc.
---
But, as @bratao mentioned above that's all getting worked through now.
Admin and maintainer permissions have been given to a group of dev volunteers / known Redash enthusiasts. CI is working again now (as of last night), and we're currently untangling the dependency hairball.
It's likely to be a few weeks (minimum I guess) before any new official releases are ready, but it will happen. :)
However, a year later, their SaaS has been discontinued. The open-source repository is now stagnant, with hundreds of unresolved merge requests. On a positive note, they recently shared the repository with some other open-source maintainers, so there's hope that Redash will be reborn.