Roadmap

We welcome participation from our user community in influencing the Zulip roadmap. If a bug or missing feature is causing significant pain for you, we’d love to hear from you, either in chat.zulip.org or on the relevant GitHub issue.

Please an include an explanation of your use case: such details can be extremely helpful in designing appropriately general solutions, and also helps us identify cases where an existing solution can solve your problem. See our guide on suggesting features and improvements for more details.

Server and web app roadmap

The Zulip server project uses GitHub projects and labels to structure communication about priorities:

• We use a GitHub project board to publicly track goals for major releases. The items with the “Done” status will be included in the next major release. Otherwise, the project board should be seen a list of priorities being considered for the release, not a guarantee that features will be included. As the release date approaches, features that will not make it into the release are dropped from the project board on an ongoing basis.

• The high priority label tags issues that we consider important. It is reviewed in the planning stage of the release cycle to identify priorities for the next release.

• The help wanted label tags issues that are open for contributions.

The Zulip community feels strongly that all the little issues are, in aggregate, just as important as the big things. Many resolved issues are never explicitly tagged as release goals.

Mobile app roadmap

We use a GitHub project board to publicly track milestones for Zulip’s next-generation mobile app.