Ordinant
Unregistered
|
 |
Posted: May 04 2006,02:15 |
 |
I fear you missed the point. My suggestion for now and the future is to always provide at least two downloads: the last stable full release for the majority of customers, and a separate beta release of the next version for a small group of testers.
As a matter of principle, I will not use beta software (except as required by my job). I work in the software industry, and the term beta has gotten way out of hand. Companies like Google leave the beta label on products like news.google.com for THREE YEARS. That is not a beta release, that is a sloppy 1.0 release that Google did not want to take responsibility for. To me, and to most end-users, the term "beta" means "not ready." Why would I want to use software that is not ready?
I am well aware that no software is ever truly finished, and that there is always something more to do. That is why developers need the discipline to take the reins, draw a line, sign their work, release whatever is ready, and then move on--on a separate development branch--with the next version.
|