We plan to make sub-version releases that only contain fixes and no new features.
For example, we would release 6.30 with some new features in FastPath. Then, if some issues are found, we would make 6.30.1 with only fixes and no new functionality. When we add a new option or feature, we would make 6.31.
6.XX.Y - only bug fixes
6.XX - fixes and feature changes
We could even make several fix-only releases in a row, if needed.
The idea is that you can upgrade to a sub-point release without risking new bugs, that could come with new features being added.
As the v6 cycle is coming to an end, there is simply no other ‘branch’ to put new features in, as v7 is still too ‘raw’. We could stop with the sub-point releases once v7 is mature enough for general use.
I would rather see the sub-point release pattern continue indefinitely.
If you want to limit only certain “feature releases” (e.g. 6.30) to long term support, so that you’re not maintaining point releases for dozens of different versions, that’s understandable. But the constant roulette of “will the new features break more than the bug fixes fix” makes upgrading a very costly process. Bug fix only release branches will greatly improve the reliability of RouterOS and make our lives as system administrators better.
+1
I vote for better bug tracking…anonymous access to http://bugs.mikrotik-routeros.com/view_all_bug_page.php shows almost no interest in resolving bugs.
It will help zilion times if there will be examples what and why was repaired instead of simple “*) pptp - fixed ~encryption got out of sync~ problem;”
Not to take away from what normis has said about it not being a Mikrotik official site, but they are only tracking 54 bugs? That includes code all the way back in 5.x routeros and several listed under RC that was never meant for public consumption. I have found my share of things that don’t work from time to time but within a version it generally gets fixed. +1 for Mikrotik giving us so many new features and keeping the network up. Cisco this past year has had so many bugs we quit counting…
It was example…anything is better than nothing…nice try without success
How they could track bugs if they do not know what was changed ?
How anyone except Mikrotik could manage such bugtracking system ?
This sounds like a fantastic idea so long as Mikrotik does not get bogged down in version management where a bug was fixed in 6.29.04 but that same bug gets re-introduced in 6.30 because the fix didn’t get pushed up into the master code (or however version management is done).
ZeroByte, that is the issue that al vendors face. I saw two bugs in the past year where they were brought back on accident but Mikrotik was very fast to fix them.
BartoszP, I think the sqlite page looks neat with the tracking and linking of issues.
This type of branching is standard in many software developments and should be kept for v7 and beyond. I think this will go a long way toward addressing many users’ fear of updating to latest point releases. One of the first advices I was given on 'tik and give to others is “they’re great. Just don’t be the first one installing new releases and even stay a point or two behind and you’ll be fine”.
I think it’s a great idea who’s time has definitely come. Thank you.
However, if I may make a request/observation as a user of Mikrotik products. Please instead of using programmers to add to 6.x feature releases…please move them to version 7 development. That way version 7 has more development power.
Please only have people bugfix 6.x after 6.30. I think we all would rather have a very stable 6.30 code with say…15 or 16 bug fix revisions added to it than have 6.35 with only 2 or 3 bug fixes on it. Extra features are nice, but bug fixes and working routers are FAR better. That way when version 7.x comes out the bugs in version 6 aren’t re-introduced into version 7.
That way version 7 can have more features when it does release AND it will have fewer bugs as there are more developers/testers working on it.
Lastly, PLEASE PLEASE start allowing for older versions of code to be downloadable. Please oh please. This will help so much out. For both firmware and RouterOS.
