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 stable
6.39 = Current, new features, could have bugs
Bugfix could have bugs too…
I 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?)
There are 3 different releases: bugfix, stable and release candidate.
Is that so difficult to understand?
A quote from the download page:
Choose Bugfix only version to download the most stable 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.
Also have a look at this post.
Bugfix=Safest
Stable=Safe with new features, new features may have bugs.
RC=Bleeding edge, expect bugs
That is precisely what I say.
6.38.7 (Bugfix only)
6.39.2 (Current) “STABLE”
6.40rc24 (Release candidate)
The bugfix Should be on the stable (assumption without errors)
Bugfix only, does not require any interpretation. He says it very clearly. They are patches.
In any case, the name should be changed.
Stable with errors
Stable with more errors
Beta future version
Of course, none really stable.
Usually the confusion about “stable” is whether this means “does not crash a lot” or “does not change a lot”.
Therefore it is not advisable to use such names.
However, before posting criticism about the available versions you should first have investigated what the meaning is.
Umm no, bugfix is just that, it is a version which 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.
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.
Let me not agree.
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)
Hello Guys, I update to this version from previous bugfix version, but my eoIP tunnel are broken, not for ping, just for voip with asterisk, IP Phones cant register across the tunnel.
I rever to 6.37.5 and works fine.
anyone whit this troubles ?
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.
PS. These bugfix/current/RC release channels only exist for roughly two years now. If curious, you can check some older forum posts out to get an idea of what the life was like before.
And they are BACKPORTS, where major bugfixes are backported to an older, more stable version than the current STABLE.
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 !
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.
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. The one that is is precisely the one to which they do not accept the observations and induce the error.
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.
The identifying legends, in the web page induce the error.
On the other hand I do not know why he feels persecuted, since you do not belong to the Mikrotik staff.
Please stop making remarks about this in this topic. When you want to discuss terminology, start a new topic.
This topic is about the newest bugfix release and it has version number 6.38.7. Whether you like it or not.
Please check the screenshot of the download page below. I highlighted the most important areas for you:
- It does contains a clear explanation of what “bugfix”, “current” and “release candidate” mean.
- The latest version in each of the release channels (“bugfix”, “current”, “release candidate” and also “legacy”) are “freely and publicly” available for download.
- And even more- most of the RouterOS versions released since Nov. 2011 are also “freely and publicly” available for download from the “Download archive” page.
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.
If you don’t like the conventions that Mikrotik is currently using that basically is your own problem, since there are a lot of other users (myself including) that are fine with it. Please just try to getting used to it. In any case, please stop polluting this thread with this naming nonsense. If you feel like you absolutely need to continue this conversation then please just start a new thread instead. Thanks in advance.