As a Hardcore LMMS user I would love to see (hear) performance improvements. 
Sure gui is nice, sure ux is important. But having a rock solid sound engine is 
top priority. And I think it's time to be able to do some audio editing in 
LMMS. Like eg Ardour. But that's just my opinion :)

Verzonden door TypeMail



Op 13 sep. 2015 19:57, bij 19:57, Dave French <dave.fren...@googlemail.com> 
schreef:
>Just my initial thoughts
>
>https://github.com/LMMS/lmms/milestones/1.2.0
>Of the 29 open issues marked for 1.2 , 11 are feature feature requests,
>What are opinions on these being moved to 1.3?
>
>There are a lot of ux/gui issues also on the list. At present there is
>a
>lot of progress in this area. We could possibly decide what ones are
>critical to this release, and then concentrate the majority of the
>gui.ux
>improvements into the next release, as this could give maximum impact
>to
>users, some of these issues maybe mute, with the current improvements
>in
>progress.
>
>Pull requests, I will do my best to comment on all the open pull
>requests
>over the next few days.
>
>Are any of our current Devs confident with the git procedures needed to
>sync changes in 1.1 in Master, or should I look into whats required for
>this?
>
>
>
>
>
>
>On 13 September 2015 at 16:46, Tres Finocchiaro
><tres.finocchi...@gmail.com>
>wrote:
>
>> There have been some rumblings of "when will 1.2 be released?"
>>
>> This is a valid question as our initial goal -- to have Zyn 2.5 ready
>for
>> the 1.2 -- release put us behind a bit more than expected and has
>allowed
>> some new features to make it in (good, bad or indifferent).
>>
>> The short answer is:  We can release 1.2 anytime and now is a good
>time to
>> start the release candidate process.
>>
>> *So what's needed to get us to an R.C. build?*
>>
>>
>>    - We have 24 pull requests that need to be decided if they go in
>prior
>>    to 1.2 or in the next release.
>>    - We have 29 bug reports tagged "1.2" that need to be decided if
>they
>>    in prior to 1.2 or in the next release.
>>    - Once ~53 items are decided, we need to merge forward any 1.1.
>>    bugfixes to master that never made it in.
>>    - Once merged/fixed/decided, we need to branch master into a
>>    stable-1.2 branch
>>       - master will continue to receive new features
>>       - stable-1.2 will only receive bug-fixes
>>    - We release a 1.2 release candidate.  We back-version these.  The
>>    version will be:
>>       - RC1 - 1.1.90
>>       - RC2 - 1.1.91
>>       - RC3 - 1.1.92
>>       - RC4 - 1.1.93
>>
>>       - *Note:  *For those using pre-packaged versions (Windows,
>Apple)
>>       to help report bugs, the downloads will appear on our downloads
>page as
>>       prerelease versions (the download buttons will be yellow rather
>than blue).
>>
>>       - *Note:  *For those not using pre-packaged versions (Linux,
>BSD)
>>       you'll need to compile the stable-1.2 branch by hand.
>>    - Once we're at a time where 1.2 is stable enough for a release,
>we
>>    publish to Facebook, Google+ and our front page.
>>
>> *How can you help?*
>>
>>    - A good starting point is to help make decisions on the pull
>requests
>>    and bug reports by reading them.
>>    - Help find bug reports that need to be marked as 1.2 but haven't
>>    yet.  Don't have access to tag a bug?  Just comment and an admin
>will do it
>>    for.
>>    - We don't have much promotionally for the 1.2 release yet.
>Here's a
>>    list of features
>>
><https://github.com/tresf/lmms/wiki/1.2-features-(snapshot-from-Sept-13,-2015)>,
>>    if you have the capacity to make some propaganda.
>>
>>
>> -Tres
>>
>>
>> - tres.finocchi...@gmail.com
>>
>>
>>
>------------------------------------------------------------------------------
>>
>> _______________________________________________
>> LMMS-devel mailing list
>> LMMS-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>>
>>
>
>
>------------------------------------------------------------------------
>
>------------------------------------------------------------------------------
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>LMMS-devel mailing list
>LMMS-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/lmms-devel
------------------------------------------------------------------------------
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel

Reply via email to