Laminar Roadmap

[raquo]

I continually develop Laminar, but Laminar does not have a fixed roadmap. I fix bugs as soon as possible, but in terms of feature development, I look at what I need, and listen to what the users are asking for, and prioritize accordingly.

Open issues are far from being my entire wishlist, but are still the best indication of what I will eventually work on. Of course, there are no guarantees, not only due to my limited time, but also because the age of an issue has no bearing on my prioritization, so it's quite possible for new, more deserving, issues to continually push out older ones. See Airstream issues too.

To help me prioritize, please upvote (👍 / 🚀 / etc.) the issues that you care about. Bonus points for responding to RFC issues or upvoting other users' responses that you agree with.

---

I aim for one or two feature releases per year, with at most one of them having significant (nontrivial to migrate) breaking changes. Such releases will often start with draft milestone versions (M1 etc.) for early adopter testing. These are announced in the #news channel of our Discord. In contrast, the blog only announces final releases.

I work on Laminar a lot, but I do not write OSS code every month. My open source work is seasonal and bunched, usually peaking in the colder months, and coming to a stall for the summer. Usually I start working on a new release when I know that I will have enough available time to finish it. However, sometimes that does not work out, scope creeps, time vanishes, and an almost-finished release ends up languishing for a couple more months until I have some time again to finish it. All of this is normal.