On Tue, Apr 29, 2014 at 10:39 AM, Jonathan Aquilina
<[email protected]>wrote:
> Having them in requests will allow it to be kept track of and easier for
> me to prioritize what needs to be done.
>
Agreed. At this point, we should be discussing this on two cross-linked
bug reports. One for LSP and another for Collaborato. :)
The LSP bug report should mention the new proposed requirement of LSP is to
make the content accessible from the DAW. This is important because this
may completely change the type of CMS or the CMS module used for the
presets, projects, etc.
I still don't understand the dedicated spot for the LSP2 codebase though.
Until we settle on a direction, the bugs may be better left in main with
an LSP type tag?
-Tres
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
