I was just thinking. After the release of v6, would it be possible to just one version after that to be PURELY just a bug fix release?
As in, say 6.1. Can that only be a maintenance release and not a feature release?
I realize this is something is strived for on every release but, since v6 is such a large release it might be a good idea to have 1 or 2 to just be purely bug-squashing releases and then slowly start releasing more features. That way everyone can hit say 6.1 and start from a good base to run forward.
I might be talking out of line on this, but it was just a thought.
I guess what I am thinking is even after that. I realize that a ton of work/bugs/feature are being ironed out through the RCs. I guess I’m thinking it might be a better idea to spend less time on features and more time on stability/bug fixes.
I am definitely NOT the engineering team over at Mikrotik. I’m not even a software programmer. I was just thinking out loud I guess…
Yes. I’ll go with Intel model for software releases. They one year go to better production process and next year they go to architecture upgrade keeping production process the same.
In MT way it would be:
6.0 - New features
6.1 - Bug fixes
6.2 - New features
6.3 - Bug fixes
etc…
