I’d love to get some kind of timeline on expected completion of current features that are in the works. Or even an authoritative list of features that ARE in the works. I think one of the biggest issues users here on the forum have is that there’s no transparency regarding what is and is not being worked on. We request sensible features that should have been implemented a while ago (like 802.3ad compliant LACP supported in HARDWARE, IGMP snooping, STP/RSTP in HARDWARE - i.e. without using software bridges, etc.), but we get no information as to whether these feature are planned, in-progress, or just plain never-gonna-happen.
So how about it, MT? Can we, as loyal forum members, be granted some limited level of insight as to what features are on the product map, and a projected target date/version for release? I think those of us on the forum are smart enough to not expect those dates to be written in stone, but at least knowing that it’s being worked on and getting some level of priority in the development process would be nice.
If we make promises, we have to keep them. So we silently listen to what users want and then see how hard it is to make the most wanted features. If we fail, we try later. Sometimes we determine that we will need a new Kernel, and those come only in major releases (RouterOS v7). There are many reasons why we don’t give specific dates and features.
The thing is, we’re ok with unfirm dates. If you tell me (and most forum members) that your intent is to have xyz feature implemented by the end of 2016, we’ll be happy with that. Even if MT can’t get it finished in that time, as long as there’s communication saying that the feature was delayed but is still in active development, we’ll be happy with that too.
I’d even settle just for a list of what is actively in development, what is queued for development, and what features simply are not on the roadmap whatsoever. No dates, just the knowledge of what’s being worked on. I know many people who are going and buying your competitor’s products because MT simply doesn’t support the feature they want, and there’s no information to indicate you ever will. You’re hurting your own sales, as many of these people may not need that particular feature today, but as long as they know you intend to support it down the road somewhere, they might opt to purchase the MT products instead.
Go take a look at the Feature Request section on Ubiquiti’s online forum. They have a handful of links that make it easy to find out what features are under consideration, which have been implemented, which are future considerations, etc. UBNT doesn’t make any promises on dates, and I don’t think the MT forum users are looking for dates. We just want to know that what we’ve been asking for is either in development or never-gonna-happen. Is that really too much to ask?
It would already be a big improvement when you compiled a list of feature requests that have been received, and
categorize them as implemented, rejected, being worked on, considered for future release #n, etc.
This would save everyone from having to enter a feature request again, and it would save you time from receiving
and registering all those.
Registration in a list does not necessarily mean you are commited to doing something, it just serves as a reference.
(similar for known bugs: fixed, will not be fixed, will be fixed in a .x update soon, will be fixed in a future release, etc)
I agree - there’s no need to promise a particular release date for any given feature or set of features, etc… but at least it would be nice to know if a particular feature has been deemed worthy or not, and if worthy, whether it requires a major revision.
It is definitely not good business to make promises and then fail to deliver on them, but it’s almost as bad to get little feedback or only vague responses.
i know this thread is a bit old, but i agree with all the posts above (including agree with normis 's reply/ his point).
but im hoping that something like this list (or wiki style?) could be implemented on MTs end. even wo dates , a implemented / rejected / being worked on / considered - list (as another user pointed out) , would be very helpful in organizing these feature requests. (and would possibly help users who make future requests see what types of requests are worth even posting, or not). It may also help cut down on some emails to MT support.