Software Release Cycles
Discussions debate the frequency and pace of software releases, questioning if cycles are too slow (e.g., every 6 months) or too fast, with references to 'release early, release often' and risks like regressions.
Activity Over Time
Top Contributors
Keywords
Sample Comments
What's wrong with every every 6 months? It's not like bug fix releases aren't dropped in the meantime.
How is releasing a new version every two weeks "slow"?
They actually produce a new release every two weeks, it's just you're at a much higher risk of encountering a regression.
It just had a major release :P any faster and people would be complaining about churn !
It sounds like they need to issue smaller releases, more frequently.
Release early and often, but make sure you're fixing something broken each time?
Is just me or they take too much time to release new versions? For me it compromise my development.
They are on a 6 week release cycle. Every 6 weeks they release the changes that are ready. Sometimes the changes are large, sometimes small. Over time, rapid releases tend to get new features out sooner than delayed releases. Don’t get hung up on the version number. It doesn’t mean this is a major release, it is just the 78th release in a series.
Are frequent releases some sort of advantage?
Why a major release soon after another one? Fast release cycles?