So, I'm personally pretty happy with 1.1 now, I think as soon as we get the last commits to that Delay plugin, we can merge that and then call 1.1 done. Bugfixes only from then on. So I'm moving on to bigger things, I don't feel a need to work on 1.1 any further.
I've also now merged the memmgr branch to master. Even if there are performance issues, I think those can be tracked and fixed later. Or possibly we'll just leave them be and move on to 2.0. So I'm thinking of tentatively starting up on the 2.0 development process. Even though the paid developer project is still unresolved, there's still tons of things that can be done to further that goal. I'm thinking that 1.2 might be left as a sort of "unofficial interim non-release", which is available in its own branch, for those who'll want to play their old projects with as new LMMS as possible - the last release providing backwards compat below 2.0. The idea is, I'll start up a new branch for the 2.0 effort - call it "lmms2", short and sweet. Later on we can merge that back to master, but for now master can stay as the 1.2 branch, maybe it can later be separated into a "unstable-1.2" branch. I'll write up a roadmap for 2.0 later, with a step-by-step plan for refurbishing LMMS. In any case the first order of business is to get rid of all legacy cruft, I think I'll start there... ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmms-devel
