2 replies
by nicknielsen
by mr_m_sween
I heard the term "Rolling Release" mentioned once several years ago. This was in reference to game developers releasing patches to fix problems on PC games. Problems that frankly should not have gotten past the testing phase of the application. The idea was that the release version was incomplete or untested and would be completed later through patching or updating. I found the idea as repugnant then as I do now, but I do see the advantage of such a release from a profit-centric perspective.
The IT world moves fast, innovates fast, lives fast, and dies just as fast. By the time your current product is fully tested and completed it is likely already either "late to the party" or simply obsolete. By sacrificing the testing process you gain Early Market Presence, which is a huge factor when talking about any tech innovation. Secondly, you also base your support and updates on sales figures, that is to say that a popular product will recieve more after sale patching than a product that doesnt sell. Without this Rolling release all costs would be incurred upfront regardless of the success of the product. Cost cuts into profit, and I think you can see the flaw in that from a profit-centric perspective.
I've ranted on this model myself before but eventually I came to realize that there is nothing to be done. The genie is out of the bottle. As long as patching a product is possible, it will be used as a crutch against bug testing and fixing. I'm sorry for being the black cloud, I reall am.
This discussion is closed to new replies.
Trending Software posts
Sort by Trending