This is a great idea. Make sure the build doesn't brick anything, then push it to us and test in every day usage and dish updates weekly based on our feedback. A true beta test community that only benefits the bulk of the customer base.
Update Pulled
- Thread starter Scott Greczkowski
- Start date
- Latest activity Latest activity:
- Replies 228
- Views 22K
- Status
Having been involved in some official betas and the comments generated in their feedback forums, the downside is too many start talking about what should be added and more often than not, some things that are major changes. Efforts were made to tell us what was set in stone and that at some point it was going to be only bug fixes, not features, but that didn't seem to slow many down in their comments.
So it can be a problem to manage. I would be interested in doing official betas with Dish. I'm familiar with NDAs and such and followed them to the letter when I did some for IBM and a couple others in the days of the OS2/Windows wars.
So it can be a problem to manage. I would be interested in doing official betas with Dish. I'm familiar with NDAs and such and followed them to the letter when I did some for IBM and a couple others in the days of the OS2/Windows wars.
Easy solution - remove them from the test. A beta test isn't for feedback on what's missing or what they'd like to see added. It's to test the existing software, as-is.
The testing I was involved in with the 3D-modeling software had multiple stages that all took place long before I got involved. 2+ years earlier, it was decided what would be added. If/when those features were added, the feature-set was locked down. Then early (alpha) testing started. This was always internal too - no one outside the company saw these builds that I'm aware of. At that point, features could be removed if they didn't work right, were unstable, etc. No features would be added though. In fact, no changes that were visible (e.g., the UI) would be done either. Obviously, private beta tests and later, public beta tests, were strictly for bugs only. Features were never added in service packs either.
I really don't think dish wants us to test anything. It is kinda sad but i feel that way. Last beta we were able to download was intended for installers. It would be nice if they care about real user feedbacks like ours.
I saw someone mention that there are 10,000 people testing the software already. That's plenty. You can certainly have too many as well. You only need one person to discover a problem, have a few duplicate it, and of course duplicate internally to enter it officially in their tracker. You don't want 400 people reporting the same bug because they don't research it before submitting it.
Sent from my HTC One M9 using Tapatalk
Sent from my HTC One M9 using Tapatalk
Agreed. Other then dish employees I don't think they are letting anyone testing but i could be wrong.
Yes but not for installers to test... it was a code setup for installers to use when they install a 4K Joey to a non Hopper 3 system...
The 4K Joey requires the carbon interface on the Hoppers to work.
Thus the reason for this key combo.
It had nothing to do with testing for anybody.
It's scary that it's out in the wild with so much that needs to be done to it. I'm glad, as posted, that there are newer and better iterations out and to come? It was Scary But Fun (Grace Jones, Inside Story - 1986).
That's just it, it wasn't supposed to be out in the wild. But, some enthusiastic employee let it out and here we are....
If what Scott says about it being applied to non-Hopper 3's that are having 4k Joey's installed, it sure is "out in the wild". It may not have been an employee, it could have been an overzealous customer that was watching a little to closely during the install. A good portion of DISH subs are Geeks and this kind of sh!t is our life's blood. So I am not surprised that the key combo got out. This isn't the first time nor the last that something like this will happen. If it's not meant to happen, then DISH needs to do things a tad differently.
I knew I read something about this a few weeks ago in another thread.
So if the target release date for Hopper 3 and the 4K Joey is still January 28th, then I hope Dish will push out the CUI to the older Hoppers by then. Or at the very least, hopefully they'll re-activate the key combo to force another manual download of it. Otherwise it won't make sense; you'll have people buying the 4K Joey who can't use it because they have an older Hopper with the older UI on it.
Update! It is downloading now. Will see what happens. It rebooted twice before starting to download. Last time it started download without a reboot. Thank you for the heads up btw
- Status
