Constituting a Life Cycle for the Releases

[cmb]

So I guess it will be

• a new release every 3 or 4 months (longer would be too long for bug fixes)
• This time period will be divided into
  • period for collecting ideas & feature requests & their discussion (e.g. 1 month or 1.5 months)
  • voting time. The start of the voting would be the deadline for new features, but not for bug fixing which should be done till the last moment. (e.g. 2 weeks)
  • programming and testing time (e.g.1 month or 1.5 months)

That would be somewhat similar to WordPress' release cycle. They're relasing a new minor or major version every 3-4 months (scheduled in advance; feature freeze one month before the release), and usually offer a few maintenance releases as needed. As WordPress has an easy update feature, there's no need to release maintenance versions for non-current minors/majors, though.