OK, let's take a little look at firmware and beta and software development version numbering schemes.
There aren't any. Or more precisely, there are way too many.
Granted, it was decades ago, but when I was in software development for the Navy, we went thru three different numbering scheme in 2 years. Plus, all the old LASS programmers kept their old system (being phased out anyway). Later, while taking graduate courses in what we then called Computer Science, we learned each company had their own way of doing things, and sometimes different numbering schemes were used on different projects. All this applied to in house development and testing. The only almost universal convention was that the first release was usually ver 1.0. Just for fun, read up on dBase II - there was no dBase I (it was Vulcan). Some companies played games and gave higher numbers on their first release, hoping to mislead buyers into thinking it was a mature product with several releases behind it. The years may pass, but the concepts remain.
Now, does Echostar/Dish have a consistent numbering scheme, that people here know and understand? And sticks to it? And that they aren't running two or more developmental versions, and trying each in the field in turn?
We don't know. And I'm not buying the confidence of someone who is often quite useful, but has been shown to be wrong on occasion.
We will know how well developed the product is once we have reports from folks with installs, including retailers who may get to test & report early. But its the version on the streets on March 15 that counts. Good, bad or indifferent, we will know in about a week.