> As a disclaimer, I'm not active in Calligra development currently, so > my opinion may not be entirely relevant, but hopefully it will be > useful anyway. > > Wouldn't it be better to (at least for the initial release) use a > different development scheme with an alpha/beta version being released > every month or so, with no feature freeze in place? It could be more > work to manage it, but by maintaining a relatively constant stream of > pre-releases that each contains actual improvements (not only bug > fixes), you'd keep the general awareness of the project, while at the > same time having enough time to polish the applications to be end-user > ready for the first final version (2.4 or 3.0 or however you're going > to call it).
Not sure whether people have seen this. http://techcrunch.com/2011/01/11/google-chrome-release-cycle-slideshow/ - Ganesh _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
