But there is not question, it is proposition.
What we have now:
- many people who are complaints release long delay;
- when release is ready, all of them began to wait and ask about next one;
- when release is ready, almost nobody happy, because active users know about features from newsletters;
- too silent news about new version because sooo many changes and most of them already was announced.
What I propose:
frequent releases for each feature which is important for users
What it gives:
- short delay from one release to anoter (one newsletter, for example,
usually describes few new features - i.e. releases often than twice in month);
- anybody can see real steps of project, which often hidden in background and stay unknown;
- users can be happy with seeing new features, which they count as important;
- such scheme will push Community Funded Ideas action;
- more buzz in shared news: there will be significant actions to be useful product;
- of cource, developers also receive promotion for their changes, for example:
18-01-2011. Version 0.3.27: Cameron Gutman implemented hooks, which are enables hotkeys support
28-01-2011. Version 0.3.28: Timo Kreuzer and Michael Martin significantly reworked our Explorer
05-02-2011. Version 0.3.29: Alexey Bragin says about serious improvements in Devices Manager & New Hardware Wizard