It was kinda hard for me to think of that as I was under stress as this router is a main router for a whole building. It was my mistake anyway… I shouldn’t have upraded the router but when I saw that after 6.21 immediatelly came 6.21.1 I thought maybe, just maybe after so many v6 version this is finally a stable one…
I would like to. I tried several times but it had never finished.
Again, I have tried on a few occasions, sometimes they work, others they hang.
But what you are not understanding Normis, is that I should not have to be doing this in the first place!
This is all what a BETA tester should be doing. Not a customer using the most recent “stable” firmware. If someone wants to test firmware, and has the time to experiment, GREAT! But do not subject users to this on the “stable” branch.
Normis, please read what I said, and instead of addressing the most useless part of my entire post, stop and consider its overall meaning/impact.
Something needs to change with Mikrotik’s firmware release policy/system/schedule!
Normis,
I am not an employee of mikrotik, test you, stop using the purchasers of mikrotik as testers.
+1
Agreed 100%.
+1
Agreed 200%. Especially at the CCR topic.
yes +1
Normis?
Clearly you can see I’m not the only one who thinks this.
There is a real problem that needs to be solved with MT’s methods of releasing firmware.
MT also needs to absolutely STOP releasing hardware that is dependent on BETA level firmware (v6 is BETA, don’t even try calling it stable). This really screwed a lot of users! If I could run my CCR on v5, I would gladly do it.
People in our market need our products to WORK without stopping. Performance is “nice” but not the major issue. When the routers are rebooting and jamming etc… They are one thing = GARBAGE!
I have worked with many vendors, as well as software developers. I have NEVER seen such an unorganized disaster as Mikrotik’s firmware methods. You guys need to clean up your procedures, and have proper ALPHA/BETA/STABLE groups. This way the people who want to play with BETA can do it and are aware of it, and the ones who want to use stable can stick with stable and not worry.
Right now you don’t even have stable (6 is not stable, please never never call it stable, it is not stable. It is untested guessing.).
6 needs to be frozen feature-wise, and stabilized. Nothing else added or changed. Make your NV2 changes and improvements etc on v7 or something else.
Sorry I am just echoing the same thing I said before, but it is simple common sense, and I don’t understand why Mikrotik can’t see the current system is unacceptable.
Don’t apologize m8. It’s Mikrotik who should be apologizing… but you wont live to see that. You didn’t just say what was already said in this thread. The same thing has been posted in almost every thread announcing a new RoS release since v.5x. Nothing has changed and I doubt anything will.
With due respect, Mikrotik must implement the appropiate test suites to see the problem before clients face it. Full stop.
Specially if the bug breaks any current feature or makes the router unavailable (reboots, port flaps, high CPU usage…). Do it using different alpha/beta/stable branches, do it using separate packages (as with wireless-ng), or use whichever other way you see fit.
I’ve worked with lots of different manufacturers, OS’es and systems (storage, network, database, security…) and none of them have a “perfect” update procedure, but Mikrotik is among the worst. For me isn’t the worst, at least Mikrotik have decent support and relatively fast response times to bugs…
An adecuate update policy is the feature that Mikrotik needs, ASAP please
+9999. The next few releases should ONLY contain bug fixes, no new features etc.
TO: MikroTik
FROM: User at large
RE: MikroTik products
As a relatively new user of MikroTik products, specifically routerboards and such, it saddens me to see such poor Quality Control on your software releases. I do not expect a reply on this email, but hear me out!
I have been in IT for over 20 years, I have used a great many products produced by companies such as Cisco, Microsoft, SonicWall, WebSense, etc. as well as a great many different Linux distros. The biggest complaint I personally have would be against Microsoft for their horrible patching system and the number of bugs they allow out the door when they release a new version is pitiful!
With your latest 6.21.1 release, it seems to me that you have now digressed to the extremely low level of Microsoft in terms of “get it out the door, we’ll fix the bugs later!” kind of mentality. It disappoints me that such a great product 8 months ago when I started learning these heavily, now has deteriorated to such a low level.
I must concur with the several posts that it is time for MikroTik to get a formal alpha-beta-stable cycle and structure. This company has grown large enough that version control will do you in unless you get a handle on it NOW. It should have already been taken care of to avoid this type of screw-up. I, for one, will back off my pro-MikroTik stance and start using Cisco products a little more heavily again until this type of issue is corrected for future prevention, not just to get this 6.x.x.x.x whatever build out the door!
I have replaced a great many Cisco products in the last 6 months with MikroTik, and was getting ready to start some maintenance cycles to upgrade them, however, at this point I am unwilling to do so, and if a stable version 6.2x.x.x.x whatever doesn’t come out shortly and stabilize this whole mess, I may have to start replacing the MikroTik systems with newer Cisco gear again, and move off the MikroTik product. At this point, I cannot, in good conscience recommend MikroTik as a stable, enterprise class alternative to Cisco.
Respectfully,
Jay Lytle, Senior Consultant/Owner
JSSM Consulting
v6.22 is released!
http://forum.mikrotik.com/t/6-22-released/82846/1