+1. it's fine by me, I think it's a great way of keeping track of what you're using and what to expect from net ROS versions. And as you mention a wa for people to upgrade according to their needs, for instance "6.30.3, Ok, a must for my production router" or "6.31, this will go into my lab's CRS to check what these guys are up to."
Count me in for testing.
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.
Any comments about this idea?
All the Best
David Gonzalez H
TikAcademy :: Training and consulting Services
Mikrotik: MCT, MTCNA, MTCRE, MTCWE, MTCIPv6E, MTCUME & MTCTCE