We could stop with the sub-point releases once v7 is mature enough for general use. The idea is that you can upgrade to a sub-point release without risking new bugs, that could come with new features being added.Īs 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 even make several fix-only releases in a row, if needed. When we add a new option or feature, we would make 6.31. Then, if some issues are found, we would make 6.30.1 with only fixes and no new functionality.

We plan to make sub-version releases that only contain fixes and no new features.įor example, we would release 6.30 with some new features in FastPath.

The idea originally came out of this thread and after a flurry of positive commentary, it became a working practice shortly therafter. We will not to intensive testing before publishing these, only quick check if upgrade can be done and if most features work fine. And finally the Release Candidate is more likely to a nightly build. The Current release contains the same fixes but also new features and other improvements, sometimes also less critical fixes than in Bugfix. Graphical Overview of the new development cycleĪ small addendum: the Bugfix only will only contain verified fixes, and no new features. Release Candidate – The release candidate will remain the development build for the next “current” release.

There will now be three different tracks of development:īugfix only – When a current build is released, only fixes to known bugs will be added to this branch of developmentĬurrent – Current release will contain bugfixes and new features As we all patiently await the release of RouterOS (RoS) v7 beta, MikroTik has announced a change in the way RoS development is organized.

Mikrotik update routeros