Or I'm very silly and I do not understand anything.
We are with version 6.39.2 and get bugfix of 6.38.7
How does it apply to 6.39.2?
6.38 = Bugfix, proven to be stableOr I'm very silly and I do not understand anything.
We are with version 6.39.2 and get bugfix of 6.38.7
How does it apply to 6.39.2?
Also have a look atthis post.只选择错误修复版本下载最圣able release without new features, just most important fixes. Choose Current to have the same fixes including improvements and new features, or choose Release candidate for testing the absolute latest builds in test environments.
Bugfix=SafestI understand that version 6.39.2 is the stable version, since it is the latest version available on the mikrotik website to download.
This is version 6.40rc24, which is the one that can have errors, since it is a Beta.
There is no sense in mikrotik web version 6.38.7 if it is only about patches. (Where is the full version?)
That is precisely what I say.There are 3 different releases: bugfix, stable and release candidate.
Is that so difficult to understand?
Bugfix only, does not require any interpretation. He says it very clearly. They are patches.Bugfix=SafestI understand that version 6.39.2 is the stable version, since it is the latest version available on the mikrotik website to download.
This is version 6.40rc24, which is the one that can have errors, since it is a Beta.
There is no sense in mikrotik web version 6.38.7 if it is only about patches. (Where is the full version?)
Stable=Safe with new features, new features may have bugs.
RC=Bleeding edge, expect bugs
嗯不,只是错误修复,这是一个版本contains no new features and only bugfixes. It has also been tested and running in the wild a lot longer than than the "current" version.That is precisely what I say.There are 3 different releases: bugfix, stable and release candidate.
Is that so difficult to understand?
6.38.7 (Bugfix only)
6.39.2 (Current) "STABLE"
6.40rc24 (Release candidate)
The bugfix Should be on the stable (assumption without errors)
Let me not agree.嗯不,只是错误修复,这是一个版本contains no new features and only bugfixes. It has also been tested and running in the wild a lot longer than than the "current" version.That is precisely what I say.There are 3 different releases: bugfix, stable and release candidate.
Is that so difficult to understand?
6.38.7 (Bugfix only)
6.39.2 (Current) "STABLE"
6.40rc24 (Release candidate)
The bugfix Should be on the stable (assumption without errors)
Current is stable, but contains new features and bug fixes. It hasn't been running in the wild as long as the bugfix version.
With new features comes the potential for new bugs, this is why we prefered the bugfix version over current.
This naming convention is not something unique to Mikrotik, a lot of software vendors follow the exact same naming convention.
It does. Mikrotik does it now because a lot of users (especially those who operate hundreds or thousands of Mikrotik devices) have been insistently asking for this for many years. The overall quality of the current releases is not even closely comparable to the overall quality of the bugfix releases, and quality is something that does have a huge value to those making business using Mikrotik products.Posting patches for a version that is not current, does not make sense.
And they are BACKPORTS, where major bugfixes are backported to an older, more stable version than the current STABLE.Let me not agree.嗯不,只是错误修复,这是一个版本contains no new features and only bugfixes. It has also been tested and running in the wild a lot longer than than the "current" version.That is precisely what I say.There are 3 different releases: bugfix, stable and release candidate.
Is that so difficult to understand?
6.38.7 (Bugfix only)
6.39.2 (Current) "STABLE"
6.40rc24 (Release candidate)
The bugfix Should be on the stable (assumption without errors)
Current is stable, but contains new features and bug fixes. It hasn't been running in the wild as long as the bugfix version.
With new features comes the potential for new bugs, this is why we prefered the bugfix version over current.
This naming convention is not something unique to Mikrotik, a lot of software vendors follow the exact same naming convention.
If we have a current version, the patches are for that version.
If we have as the case of Mikrotik a version in development, we know that it has not been sufficiently tested and is in BETA version.
Posting patches for a version that is not current, does not make sense. Which is what happens with Mikrotik. But so that they publish a version that is not Beta, nor is it Stable? (6.39.2)
In software development, the ALFA versions are worked, which are those that are being developed. They are not published.
There are the BETA, which are not yet in production but are available for testing.
They are the STABLES, which are those that are made available to customers and on which if a BUG is corrected. (Are in production)
The most stable version of any feature is the current bugfix-only version. If you find problems when using the current bugfix-only version, then submit a report to Mikrotik Support detailing the problem you have.Did anyone tested the multicast package? Which version is the most stable that does not lag?
Excuse me, but nowhere on Mikrotik's download site does it say the latest stable release.And they are BACKPORTS, where major bugfixes are backported to an older, more stable version than the current STABLE.Let me not agree.嗯不,只是错误修复,这是一个版本contains no new features and only bugfixes. It has also been tested and running in the wild a lot longer than than the "current" version.That is precisely what I say.There are 3 different releases: bugfix, stable and release candidate.
Is that so difficult to understand?
6.38.7 (Bugfix only)
6.39.2 (Current) "STABLE"
6.40rc24 (Release candidate)
The bugfix Should be on the stable (assumption without errors)
Current is stable, but contains new features and bug fixes. It hasn't been running in the wild as long as the bugfix version.
With new features comes the potential for new bugs, this is why we prefered the bugfix version over current.
This naming convention is not something unique to Mikrotik, a lot of software vendors follow the exact same naming convention.
If we have a current version, the patches are for that version.
If we have as the case of Mikrotik a version in development, we know that it has not been sufficiently tested and is in BETA version.
Posting patches for a version that is not current, does not make sense. Which is what happens with Mikrotik. But so that they publish a version that is not Beta, nor is it Stable? (6.39.2)
In software development, the ALFA versions are worked, which are those that are being developed. They are not published.
There are the BETA, which are not yet in production but are available for testing.
They are the STABLES, which are those that are made available to customers and on which if a BUG is corrected. (Are in production)
This is exactly what the Mikrotik bugfix-only version means.
And you still get bugfixes for the current STABLE version in theMmikrotik "current" tree.
Everyone understood it or made an effort to adapt their own usual vocabulary.
Could you now please stop harassing us and let this thread serve its original purpose : which is to let the people migrating from the previous bugfix (6.37.5) to the new bugfix (6.38.7) warn us about problem that might arrise ?
Thank you !
Please stop making remarks about this in this topic. When you want to discuss terminology, start a new topic.Excuse me, but nowhere on Mikrotik's download site does it say the latest stable release.
Please check the screenshot of the download page below. I highlighted the most important areas for you:Excuse me, but nowhere on Mikrotik's download site does it say the latest stable release.
It only says only bugfix for a version that is not freely and publicly available on the Mikrotik site.
This is just a naming convention. A lot of naming conventions exist, and none is universal enough to make everybody happy. My favorite example is the branch naming convention that FreeBSD project is using (I find it somewhat similar to what Mikrotik is currently using), where "current" means the one that they are currently working on (i.e. bleeding edge), "stable" means it only receives some fixes that were previously committed to "current", tested for some time and are considered stable enough, and "release" means only security fixes are allowed in.Bugfix only is not the same as stable or current
Current means current latest version
Release Candidate is the one you are working on.
Clearer impossible and it would be good for those who clarify how things are the mikrotik staff.
Oh Dear I am really confused cause i am a Learner and also working in a Network and i can configure Little ....Bugfix could have bugs too...
feature set - all features old and new that is present in that particular minor version...Actually major does need to correspond to kernel and minor and subminor do not need to correspond to feature set or patch too. Just see the release notes and you will find that subminor is adding new features too while minor is patching old problems also...
Why are you always confusing download channels and versions??
Current/bugfix/RC in download page is download channel, is whatever version MikroTik choose to position there, v6.39.2 can be placed in bugfix also, if MikroTik sees it fit. So these channels is nothing more as MikroTik's suggestions for you at this particular time - you can choose to go for stability [bugfix], sweet spot between new features and stability [current], of go for all the newest features [RC].
If we talk about version numbers itself
v6.38.7 - v6 [Kernel version]. 38 [feature set version]. 7[ patch version for this feature set]
v6.39.2 - v6 [Kernel version]. 39 [feature set version]. 2[ patch version for this feature set]
v6.40rc25 - v6 [Kernel version]. 40 [feature set version]. rc25[ progress of new feature set implementation]
Bottom line: download channels and version numbers are two different things.
Full name is actually "Bugfixes only", it means this version will only get updated when serious bug is found. Normally it stays, as it is proven to be highly stable.
Current means the actual running version which is updated often.
RC means candidate for becoming Current. It is released daily without much testing. DO NOT USE THIS unless testing on separate device.