The team has a 6-12 months high-level [[Roadmap]], which defines high-level themes and features to be addressed in this timeframe.
We work on a roughly six-week iteration schedule. That means, a new minor/major release every six weeks if everything goes as expected.
The six-week-cycle is commonly adopted in the web development ecosystem. E.g., the two major browser vendors, Chrome and Firefox, both promoted a six-week release schedule. It is also recommended by the Basecamp team.
We work in weekly segments:
- Week 1-2:
- Address critical issues uncovered in the previous iteration
- Reduce debt introduced during the last iteration
- Plan the next iteration
- Week 3-5: Work according to the plan
- Final Week: Endgame
- The team tests the new features according to a test plan and updates the documentation. - We make a pre-release available on the ‘next’ channel and invite users to help us test the pre-release.
- Week 1 (next iteration): - monitoring the pre-release and fixing critical issues. - publish the release to the ‘latest’ channel, sometime midweek, after 24 hours with no changes to the pre-release.