In general, I like the idea of aiming for consistent release cycles.
However, every month is just too much, at least for me. There is a
considerable overhead associated with each release for end-to-end
performance tests, tests on different environments, code freeze for new
features, etc. Hence, a too short release cycle would not be "agile" but
would actually slow us down. From my perspective, a realistic release
cadence would be 2-3 months, maybe a bit more for major releases.
Regards,
Matthias
On 1/5/2017 8:51 AM, Luciano Resende wrote:
I would like to propose a more consistent release cadence. The release
early, release often mantra is good to increase community interest, and
also enable users to provide feedback sooner on the areas we are developing.
How about releasing every month? Maybe we do something like development
phase on the first three weeks of the month, and stabilization/test/release
on the last week? This would align with the proposed next release date from
Mike Dusenberry (Feb 1st) on the roadmap thread.
