munteanadrian88

It was aimed at readers who have enough software knowledge and know that some bugs are easy to fix, but they don't have experience of professional test departments so they don't know that even a simple fix requires a LOT of testing. 
Grief, I bet I get as impatient as the financial dept does when a product is not released, but I have a lot of respect for managers who listen to the testers when they say "no, can't release it yet". We can only assume if the company had more resources they would throw them at testing, but what do we know? The same rules don't apply to every product or every company.
Anyway, I hate waiting too, but you know at least NetDuma actually release updates, some companies never seem to even do that.
 

Often people who don't know software testing inside out don't grasp that you can't just change a line of code, test it and then release the product. I remember a one line bug that was fixed but an  intel development team. It was an easy fix. They tested the change but  ignored the "golden rule" in the book of software testing and released the product. The change they made had a knock on effect and caused a fatal bug in a completely separate piece of code. It was hundreds to one against, but it happened. The worst part was that it only became apparent months later after it had caused millions of dollars of damage to projects all over the world. intel's reputation was badly damaged, the product destroyed. intel sacked the entire development team.
I have no clue who you were referring to by mentioning those nice words from the above: "Often people who don't know software testing inside out don't grasp that you can't just change a line of code..."
Maybe not all the people in this thread could be classified as "really don't know anything abut software testing..."
I personally work since 2014 in software testing and gathered a lot of experience over the years from that (so please be nice when addressing to the public) 
NO one says change a line of code and that will fix all the issues in the firmware
All in all, nice story about the fatal bug
The golden rule is - when a product is tested, don't just test what you think you need to test - test it all! That's why it's so slow to test even a simple change. And it's best to save a number of fixes up to justify the time spent testing. All in all, it just takes far more time than you would think.
Go tell your boss you will need more time that he can imagine and see what happens  
That's why you have to obey another golden rule in order to test SMARTER not HARDER.
GO GO test automation!

Often people who don't know software testing inside out don't grasp that you can't just change a line of code, test it and then release the product. I remember a one line bug that was fixed but an  intel development team. It was an easy fix. They tested the change but  ignored the "golden rule" in the book of software testing and released the product. The change they made had a knock on effect and caused a fatal bug in a completely separate piece of code. It was hundreds to one against, but it happened. The worst part was that it only became apparent months later after it had caused millions of dollars of damage to projects all over the world. intel's reputation was badly damaged, the product destroyed. intel sacked the entire development team.
The golden rule is - when a product is tested, don't just test what you think you need to test - test it all! That's why it's so slow to test even a simple change. And it's best to save a number of fixes up to justify the time spent testing. All in all, it just takes far more time than you would think.

Nothing extra to add unfortunately. Difficult to say but most likely, possible the XR1000 may release around the same time as the 500 - depends on NG and how far they are in their processes and whether any issues are found etc.

Welcome to the forum!
We're not sure exactly where it is in their testing process, we are still working with them quite intensely on XR1000 firmware at the moment, but I at least was under the impression the last version we sent over was ready for their testing and that it would be released first. I'll speak with the team and if there's any further update we can provide on it, we'll update the firmwares page mentioned above accordingly.

Now we are in October and still NO Duma OS 3.2 on the XR1000 🤔 Why does ist take soooo Long? 

Interesting, looks like it may be allowed on our side which is why you can't block it, I'll double check it and if so remove it so it can be blocked. 

On each page unpin any panels that have the pin icon solid white and that will get rid of the error. 
In regards to the two different servers, there are many different servers clustered in one location so blocking one in a location won't block other servers in that same location. Remove the block from Allow/deny, then block it again but give it a name, then disconnect from the server for a least 2 minutes - it should no longer appear on the map after this, then search again and it should be blocked.
We're looking into the issue some are having with reporting.

It shouldn't matter, you should still be able to click Deny and you won't get matched with that server again. Is that not the case for you?

The peers will be misclassified and should show as servers, as you can see on that peer it has a domain name consistent with a google server, it will not impact you negatively, it is just a visual thing on the map.

All our changes are done now so it's up to them whether they want to release as is or test or add their changes & test etc. If we get more info on what they're planning to do we'll update the table

Hello Liam, Fraser,
When will DumaOS 3.2 version be available for consumers?
 Is there a due date for the 3.2 final release?
All I know so far is this:

Best Regards,
Adrian M.

Hi Adrian, we don't give out dates for betas or firmware releases, any new information will be put in that table so you can see at what stage we are at. Assuming testing goes well it will likely change to preparing for release or something similar so you know it could release pretty quickly.