Some words about UPDATES

We are developing a software solution based on MikroTik boards.
This software uses quite a lot features and it controls the boards using API.

Everything would be fine if there were no updates.
We still have to work with version 3.17, because it is the only version that does not contain major bugs in the api or other related things.

Some history:

version 3.17: mail does not work correctly (we can handle that)
version 3.20-3.22: new api commands (query) (nice), =disabled= switch totally disappeared (hole version useless :frowning: )
version 3.23: =disabled= switch reappeared (nice), problem running scripts from scheduler (hole version useless)
version 3.24-3.25: scripts are ok again (nice), =comment= switch in api totally dissappeared (hole version useless)

I don’t quite know what Your internal buisness policies are, but I assure You:
If You continue throwing updates in a way like this, there will be quite a lot people that get pissed off that much like we are.

Perhaps You guys should better spend double time in QA than developing new features.

The next version is better be working or You’ll get much more unsatisfied clients.
This one has the problem too, by the way:
http://forum.mikrotik.com/t/this-is-really-annoying-please-stop-doing-it-or-fix-it/29289/1
And yes, a reference manual for api would be very useful. The puzzling to get the commands right is VERY anoying.


An unsatisfied customer

what kind of problem?..

My colleague tested running a script by a scheduler which did not work (no script-run triggered).

I can confirm what op said about 3.23, but then again… you dont upgrade your routers before you have tested that the new releases works with your scripts/setup etc..it doesnt work ? dont upgrade, but submit a bug report.

why I asked that - I have checked before posting, it worked…