On Wed, Jan 28, 2015 at 07:45:47AM +0200, Vesa wrote: > As for the freeze, I think we talked of February before? Maybe a week or > two from now? Is anyone working on any big features right now?
Well, I am not asking too much, my idea would be just to not tag any new feature/enhancement as 1.2 and remove the 1.2 tag from any unrealistic issues like huge features or bugs that are seemingly impossible to solve. We don't need actually to freeze development, one can continue working on what they want, it's just that we would try to stabilize the 1.2 release. Providing a release candidate and asking the community to test it would be great to trace bugs that can be squished that are easy to fix or were introduced in this release, this would increase the quality of LMMS releases a lot. Looking right now this is the stats for issues tagged 1.2: Open: 56, Closed: 68. So even if we stopped right now tagging issues to 1.2 we would have *a lot* of stuff to do, even though a lot of these issues are bad described enhancements or bugs outside of lmms scope. As for the next release being 2.0, I don't know. I would rather be careful and try to take little steps as I know everyone has a lot of expectations for 2.0 (and I know that I can't develop all these incredible new features/core refactors/bug squashing myself for now). ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
