Release early, release often (also: time-based releases, sometimes abbreviated RERO) is a software development philosophy that emphasizes the importance of early and frequent releases in creating a tight feedback loop between developers and testers or users, contrary to a feature-based release strategy. Advocates argue that this allows the software development to progress faster, enables the user to help define what the software will become, better conforms to the users' requirements for the software, and ultimately results in higher quality software. The development philosophy attempts to eliminate the risk of creating software that no one will use.
The alternative to the release early, release often philosophy is aiming to provide only polished, bug-free releases. Advocates of RERO question that this would in fact result in higher-quality releases.
Open-source software, at heart, is a method for maximizing the efficiency and speed with which one can create the next version. Release early, release often, is the mantra, meaning get your new code out into the public so millions of eyes can tear it apart and help create a new version even faster
This practice is described as "release early, release often." The open source community believes that this practice leads to higher-quality software because of peer review and the large base of users who are using the software, accessing the source code, reporting bugs, and contributing fixes.
Essentially, both philosophies [Release Early, Release Often and Minimum Viable Product] attempt to eliminate the risk of creating software that no one will use.
Release early. Release often. And listen to your customers.
We come from the world of open source, which is all about "release early, release often" rather than highly polished releases
Manage research, learning and skills at defaultLogic. Create an account using LinkedIn or facebook to manage and organize your IT knowledge. defaultLogic works like a shopping cart for information -- helping you to save, discuss and share.