Quote:
|
As long as we're debating friendly FIRST style, what alternate solution would others propose?
|
Well, depending on the type of beta required, many beta tests could be made open betas. For example, what would a public beta of CAN require? New software libraries and a few cables. FIRST/WPI/whoever would need to provide libraries anyway for a closed beta.
Yes, that does mean more strain on FIRST/WPI to respond to bug reports,provide support, etc. But...that's really what has to happen for the product/system to mature. If 300 teams are emailing because they can't figure out how to configure something, it means the documentation's not clear. If FIRST gets 1000 bug reports for various things, it's a lot more work for them, but as long as they can be prioritized and dealt with, it means that teams AREN'T going to hit those issues during build season.