>
> We already have a sort of unofficial feature freeze. Large new features
> won't be merged anymore until we branch out 1.1 to its own branch.
> Smaller new features that aren't likely to cause instability - such as
> your vst/sf2 commit - can still get in...
Ok, so the plan is to refine those features already committed?
The reason I ask is because I would like the team to offer official OSX
download, but I don't feel comfortable with the stability until a few bugs
are fixed.
Is there a chance of putting priority on some of these? I believe two of
them to have to do with mutex thread handling with the clang compiler,
which I don't know enough to help with.
Furthermore, since we'll be getting two new synths, we may want to put some
pressure on the team (i.e. unfa) to get some presets made for the 1.1
release.
These items are much easier to reach out for help on from both a
development and testing perspective if we identify what our goals for 1.1
are. Does that make sense?
------------------------------------------------------------------------------
"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
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
