[Feature Request] Public roadmap

Hello

It would be great if a roadmap (for software at least), just like GitHub[https://github.com/github/roadmap\] does, with detailed [schedules](GitHub Public Roadmap · GitHub).

That way we can upvote/provide better feedback on the direction things are going, which is really difficult now given the feedback can only be provided after the features are implemented, plus it makes us (at least in my case) doubt more about device purchases given it’s difficult to asses the direction/priorities of some things.

If it works great for GitHub, I don’t know why it couldn’t work here.

Thank you very much.

1 Like

Does any hardware vendor has the same?

1 Like

Not that I’m aware of, but that doesn’t mean others do it right either.

I understand for regulatory and competitiveness, a roadmap for devices might be less desirable for the team. However, I don’t see the competitive advantage that a software roadmap could give: RouterOS, at the end of the day, is a nice UI over Linux kernel, everything that’s already possible in Linux is somewhat possible in every other vendor. But the focus/QoL improvements are unique to RouterOS.

Mikrotik does not only sell hardware, but also the software (CHR). When you buy the hardware, you know the specifications and live with them for the rest of the day, but not when you know the software: you only know the value at the time of purchase. If you could have some hints on the future direction, you have more confidence buying.

A completely useless request, which will be ignored like all the other identical ones already made over the years.

1 Like

Can you share why you think so? What’s the point of take the time to reply in a thread with non-constructive feedback?

Ever since v7 came out, EVERYONE has been asking them to stop adding things, match the features of v6,
fix all the bugs, release a long-term release,
and then if they want to add anything else, let them do it in versions not called "stable"...

But imagine if they've even listened to one of these requests...
Imagine if they have to publicly release "deadlines" to meet...

4 Likes

A necessary clarification:
The tone is due to frustration with what I wrote in the previous post, not because of you.

1 Like

Thank you very much for sharing and don't worry, I didn't take it personally. Trust me I understand your frustrations, because I share them to some extent (one of the reasons behind opening this thread): I see that some priorities for the team are mismatched with customer expectations. That's why I wanted you to share your points (and because perhaps you thought of any reason I didn't thought of beforehand for mikrotik not to do it, like my example with the devices, which is the only one I can think of).

Personal point: I've been a customer for both Mikrotik and Ubiquiti and I've seen how the latter has been in an spiral of losing their way: both U6 and U7 were extremely buggy at launch (U6 is much better now, but not as good as the AC series) and, instead of fixing these ASAP, it took them years, while releasing a NAS, UPS, Cameras… even a car charger! Nothing nobody was asking them for. Don't get me wrong, it's fine to explore other lines, but only do it when you excel at your main area, without losing the focus on your main customers.

The current situation with CAPsMAN, although it works, is completely unsustainable long-term because differentiating between them is really difficult (at this day, we don't have an explanation if why a newer CAPsMAN was required), I've had some issues with PPPoE in the latest release as many (and I specially would like to know if further much-requested improvements to PPP interfaces are on the way, or we should expect complete immobility in that regard).

I really hope this disconnection with customers could be fixed with this roadmap. Because there are only two reasons for not acknowledging feedback: either they don't care, or either they truly don't know what their priorities should be. A roadmap would be beneficial for both of us.

Mikrotik already have a public roadmap.

It's the change log of the “Testing” release channel. These are all planned changes/features that will eventually make their way into the “Stable” release channel.