I know that there’s older versions of code that Mikrotik has on the download page…however I don’t believe that it is sufficient. The code that is there is WAY older…not just a few versions back.
It also seems like with the differences/bugs between versions of code that it almost might be beneficial for us as users to choose which version of firmware we should use depending on our needs.
Would it be too much to ask for a release starting version 5 to go all the way to present with every official released version?
I think the real request here is a more reliable versioning scheme… basically “bring back the 3 tier version vectors” - minor version is bug fixes only, middle number is new features, without any breaking changes to older scripts, and the major number is new and/or breaking changes.
Assuming such a policy is followed, that would ensure that a script written for 6.0.0 can run on 6.., while a script for 6.1.0 can run on 6.1., 6.2., etc. but probably not on 6.0.* and not necessarily 7.0.0 or later.
If that sounds like tying your hands too much, you can do a 4 tier versioning scheme, where the major number is given whenever you make “hardcore breaking changes”, and the middle one is given for “some breaking changes (removed/renamed some stuff), but not across the board”. e.g. 6.0.0u1 will be the first bug fix release for 6.0.0, while 6.0.1 will be including some non breaking changes (e.g. like how “export compact” was).
What is the reason for wanting reliable versioning scheme? Simple: The ability to copy&paste appropriate scripts, rather than always having to rewrite them every few (minor!) versions ahead.
Of course, I’m aware of the reason for not having it - that some people get confused by it. Something with more letters in it could clear up such a confusion, e.g. 6.0sp2u1.