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?

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.

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?)

Bugfix=Safest
Stable=Safe with new features, new features may have bugs.
RC=Bleeding edge, expect bugs

There are 3 different releases: bugfix, stable and release candidate.
Is that so difficult to understand?

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)

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?)

Bugfix=Safest
Stable=Safe with new features, new features may have bugs.
RC=Bleeding edge, expect bugs

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.

There are 3 different releases: bugfix, stable and release candidate.
Is that so difficult to understand?

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)

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.

There are 3 different releases: bugfix, stable and release candidate.
Is that so difficult to understand?

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)

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 ?

Posting patches for a version that is not current, does not make sense.

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.

There are 3 different releases: bugfix, stable and release candidate.
Is that so difficult to understand?

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)

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)

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 !

Did anyone tested the multicast package? Which version is the most stable that does not lag?

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.

There are 3 different releases: bugfix, stable and release candidate.
Is that so difficult to understand?

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)

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)

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 !

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.

Excuse me, but nowhere on Mikrotik's download site does it say the latest stable release.

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.

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.

Please check the screenshot of the download page below. I highlighted the most important areas for you:

1. It does contains a clear explanation of what "bugfix", "current" and "release candidate" mean.
2. The latest version in each of the release channels ("bugfix", "current", "release candidate" and also "legacy") are "freely and publicly" available for download.
3. 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.

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.

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.

Bugfix could have bugs too...

Oh Dear I am really confused cause i am a Learner and also working in a Network and i can configure Little ....
I need help from All seniors Guru's ......

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.

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...

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...

feature set - all features old and new that is present in that particular minor version...

From my experience:

1) "Bugfix" = Final stable version. Only this should be installed on production router.

2) "Current" = Public beta version with bugs for public beta testing, but have official support via support@mikrotik.com. You can install it on own risk.

3) "Release candidate" = beta version with bugs without official support.

Do not be silliy since there is no RFC for releases labeling. Mikrotik is free for using its own system. Use bugfix for higher security. Bugfix is auto-explanatory. For me current is safe enough and love having RC's available with latest features although it is more risky!!!

I agree with everyone's comments here. But possibly there may be one small labeling change that could stop some confusion. The current version inside the router is currently labelled as " Stable ", I think that's great, just like FreeBSD style. But we all know its not a release that works with stability. It should be named to the channel " Current ". Just like the bugfix channel is actually named bugfix in the router, so should the current update channel.


output from three versions installed as example:

[admin@Tik1] /system resource> print
uptime:
version: 6.37.5 (bugfix)



[admin@Tik2] /system resource> print
uptime:
version: 6.39.2 (stable)



[admin@Tik3] /system resource> print
uptime:
version: 6.40rc32 (testing)

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.

Thank you So much macgaiver , I got it .

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.

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.

Thank you so Much Normis ,
Now it is Total Clear....