World Library  
Flag as Inappropriate
Email this Article

Perpetual beta

Article Id: WHEBN0003342298
Reproduction Date:

Title: Perpetual beta  
Author: World Heritage Encyclopedia
Language: English
Subject: Foldit, Quantum Moves, Beta (disambiguation), Software release, Web 2.0 neologisms
Collection: Software Release, Web 2.0 Neologisms
Publisher: World Heritage Encyclopedia

Perpetual beta

Perpetual beta (or ‘banana principle’) is the keeping of software or a system at the beta development stage for an extended or indefinite period of time. It is often used by developers when they continue to release new features that might not be fully tested. Perpetual beta software is not recommended for mission critical machines. However, many operational systems find this to be a much more rapid and agile approach to development, staging, and deployment.


Perpetual beta has come to be associated with the development and release of a service in which constant updates are the foundation for the habitability or usability of a service. According to publisher and open source advocate Tim O'Reilly:

"Users must be treated as co-developers, in a reflection of open source development practices (even if the software in question is unlikely to be released under an open source license.) The open source dictum, 'release early and release often', in fact has morphed into an even more radical position, 'the perpetual beta', in which the product is developed in the open, with new features slipstreamed in on a monthly, weekly, or even daily basis. It's no accident that services such as Gmail, Google Maps, Flickr,, and the like may be expected to bear a 'Beta' logo for years at a time."[1]

Used in the larger conversation of what defines Web 2.0, O'Reilly described the concept of perpetual beta as part of a customized Internet environment with these applications as distinguishing characteristics:

  • Services, not packaged software, with cost-effective scalability
  • Control over unique, hard-to-recreate data sources that get richer as more people use them
  • Trusting users as co-developers
  • Harnessing collective intelligence
  • Leveraging the long tail through customer self-service
  • Software above the level of a single device
  • Lightweight user interfaces, development models, and business models.[2]

See also


  1. ^ O'Reilly, Tim (2005-09-30). "What Is Web 2.0". Retrieved July 7, 2009. 
  2. ^ Morris, James H. (August 30, 2006). "Software Product Management and the Endless Beta". Carnegie Mellon University. Retrieved July 7, 2009. 
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.

Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.