Public Roadmap

[WesleyAC]

It would be really useful to have a public roadmap of features that are being worked on, so that people can have a better idea of whether Rocket is currently able to support their usecases. As someone who's used Rocket for small projects (like hanabi.site), I don't have a good idea of how well it supports large projects, and when I tell my friends about Rocket, I need to make sure that they're aware that they may run into issues like #1302 / #1434. It would be great if people could get a better idea from the Rocket website of what features are basically done, what things are still being worked on, and what things are usable but likely to have breaking API changes in the future, and where they might have problems deploying Rocket today.

[Immortalin]

A faster release pace with smaller, but featureful incremental updates instead of singular big updates would also be nice. A number of important features are gated behind 0.5 right now and it is difficult to justify using it with unstable rust.

[RoKu1]

@SergioBenitez

Hey, any rough estimate for when the frameworks 0.5 version would rollout, I am thinking to use this for a very large website for a company, with a site which would have decent traffic.

[SergioBenitez]

Starting now and into the future, we'll use GitHub projects (and issues) as our roadmap. For Rocket v0.6, for example, you can view everything planned, and their progress, in the Rocket v0.6 project.