I’m not sold on the wisdom of publishing a public roadmap that your customers and potential customers can read.
I’ve released six commercial products over the past 10 years, and one lesson I’ve learned the hard way is to never make your roadmap or detailed future plans about a product public. I generalise about what I’m working on or what my long term plans for a product are, but detail leads to problems.
Example 1: The roadmap says feature X will be in the next release in two months time. For whatever reason, that release is 3 months late and feature x did not make the cut, for technical reasons or because I’ve changed my mind about its value to the product. Customers are unhappy because a promised release is late, or they’re unhappy because a feature some of them wanted is not in that release.
Example 2: “I only bought your software because you said feature X would be in it in August.” I’ve had this happen many times in early products.
Public roadmaps are hard to change, as customers have made purchase decisions on the back of what you’ve printed in that roadmap. It leads to raised expectations that are almost never met. Better to set low expectations and surpass them than high expectations that you’re unlikely to meet.