Hi everyone. Could we make a definition on what should be planned to 1.2 and stop tagging new issues as 1.2?
I've been sweeping the bug tracker trying to tackle all important issues so that we can stabilize and improve LMMS for the next release, but there are always new issues popping out, and if we continue tagging them as 1.2 we will be like Sisyphus[0] until someone gets annoyed and pushes forward with a lot of 1.2-tagged unresolved issues. This is undesirable. My suggestion is to define now if we want new features to 1.2, create and tag them, then freeze the release. This means that new issues should not be tagged 1.2, except if they are bugs that are feasible to solve before the 1.2 release timeframe. What do you think? [0]: http://en.wikipedia.org/wiki/Sisyphus ------------------------------------------------------------------------------ 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
