Release Early, Release Often
A software development philosophy advocating frequent releases to gather feedback and iterate quickly.
Also known as: RERO, Ship Early Ship Often, Frequent Releases
Category: Software Development
Tags: software-engineering, processes, agile, open-source, principles
Explanation
Release Early, Release Often (RERO) is a software development philosophy popularized by Eric S. Raymond in 'The Cathedral and the Bazaar.' The principle advocates releasing software as soon as it provides any value, then iterating rapidly based on real-world feedback.
Core tenets:
1. **Early feedback**: Real users provide better feedback than internal testing or speculation.
2. **Incremental improvement**: Many small releases reduce risk compared to infrequent large releases.
3. **Market validation**: Early releases test assumptions before investing heavily in wrong directions.
4. **User engagement**: Frequent updates keep users engaged and feeling heard.
5. **Bug discovery**: More eyes and more usage environments expose issues faster (see Linus's Law).
Implementation practices:
- Continuous integration and deployment pipelines
- Feature flags for gradual rollouts
- Semantic versioning for clear communication
- Beta/canary release channels
- Automated testing to maintain quality at speed
The philosophy contrasts with traditional 'waterfall' approaches where software is released only when 'complete.' RERO acknowledges that software is never truly complete and that iteration is essential.
For knowledge workers, RERO suggests: sharing drafts early for feedback, publishing incrementally rather than waiting for perfection, and treating work as ongoing conversation rather than final pronouncement.
Related Concepts
← Back to all concepts