Release early, release often

community-releasesearly and oftenrapid releaserelease early and release oftenRelease early. Release often.time based release cycletime-based release cycletime-based release schedule
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.wikipedia
22 Related Articles

The Cathedral and the Bazaar

Bazaarcathedralbazaar model
This philosophy was popularized by Eric S. Raymond in his 1997 essay The Cathedral and the Bazaar, where Raymond stated "Release early. Release often. And listen to your customers".
7) Release early. Release often. And listen to your customers.

Eric S. Raymond

Eric RaymondRaymond, EricESR
This philosophy was popularized by Eric S. Raymond in his 1997 essay The Cathedral and the Bazaar, where Raymond stated "Release early. Release often. And listen to your customers".
Release early, release often

Minimum viable product

MVPsmallest useful orbital rocket
Minimum viable product
The MVP differs from the open source software methodology of release early, release often that listens to users, letting them define the features and future of the product.

Vote early and vote often

voting early and often
Vote early and vote often
* Release early, release often

List of software development philosophies

development philosophysoftware development philosophy
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.

Linux kernel

Linuxkernelkernels
This philosophy was originally applied to the development of the Linux kernel and other open-source software, but has also been applied to closed source, commercial software development.

Open-source software

open sourceopen-sourceopen source software
This philosophy was originally applied to the development of the Linux kernel and other open-source software, but has also been applied to closed source, commercial software development.

Software development process

development cyclesoftware development methodologysoftware development life cycle
Software development process

Open coopetition

open-coopetition
Central actors that act as a bridge between the community and the companies contributing to it (e.g., a lead developer or a maintainer) need to act as gatekeepers (aka boundary spanners) for bugs reported against specific products sold by the participating firms. As the software is integrated downstream into specific products often sold by competing firms, it matters to sort out what bugs are the responsibility of a specific firm or the community as a whole. In parallel, such 'bridging' actors also act as gatekeepers in flows of code and information (e.g., what code should, or should not, be included in the official community-releases and what information should circulate among the ecosystem participants).

OpenStack

OpenStack SwiftSwiftNeutron
The OpenStack community collaborates around a six-month, time-based release cycle with frequent development milestones.

Perpetual beta

"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, del.icio.us, and the like may be expected to bear a 'Beta' logo for years at a time."

Jailbreak: Source

The team are using a release early, release often system to refine the gameplay constantly, using community feedback to expand and better the games mechanics.

SageMath

SageSage projectSageMath (an open source algebra program)
SageMath practices the "release early, release often" concept, with releases every few weeks or months.

Software versioning

versionversion numbermajor release
The free-software and open source communities tend to release software early and often.

Java (software platform)

JavaJava platformJava software platform
Java SE 11 was released September 2018, the first LTS release since the rapid release model was adopted starting with version 9.

ManageIQ

The ManageIQ project uses a time based release cycle where a new version is released approximately every 6 months.

Apache OpenOffice

OpenOfficeOpen OfficeApache
Apache OpenOffice does not "release early, release often"; it eschews time-based release schedules, releasing only "when it is ready".

LibreOffice

LibreOffice OnlineLibreOffice BaseLibreOffice Impress
LibreOffice uses a time-based release schedule for predictability, rather than a "when it's ready" schedule.

Eric (software)

eric
eric follows the development philosophy of Release early, release often, following loosely a time-based release schedule.

RERO

Release early, release often, a software development philosophy