Hi all, IMHO a combination of definition of a (coarse) roadmap and feature which should be included in the next version and a relatively fixed release cycle (around 3 months) works best. Part of the roadmap should also to fix all known bugs. Voting of priority of features (and hence definition which are included in next release) could be done via “dev” mailing list.
> 1. Should we define a feature set and log it inside JIRA. Then once > this set is implemented a release is done. > 2. Should we define a time cycle e.g. 1-3 months and provide releases > even if some features are not ready. > 3. A combination I could not yet think of > On 09 Oct 2015, at 23:04, Ramesh Reddy <[email protected]> wrote: > > development = 0 - 1 1/2 months > beta = 1 1/2 - 2 1/2 months > CR/Release = 2 1/2 - 3 months Furthermore the suggestion of Ramesh with different development phases sound good for me. So we can first focus on implementing the feature (dev), test intensively and polish the feature up (beta), and then do the release (CR). Best Regards, Michael
smime.p7s
Description: S/MIME cryptographic signature
