On 01/28/2015 08:35 AM, Amadeus Folego wrote:
> On Wed, Jan 28, 2015 at 07:45:47AM +0200, Vesa wrote:
>> As for the freeze, I think we talked of February before? Maybe a week or
>> two from now? Is anyone working on any big features right now?
> Well, I am not asking too much, my idea would be just to not tag any new
> feature/enhancement as 1.2 and remove the 1.2 tag from any unrealistic
> issues like huge features or bugs that are seemingly impossible to
> solve.
The tags are morelike guidelines. Or aspirations... they're more like
what we /aim /to get done for a given release, but it's very common for
issues to get bumped ahead when they don't get addressed in time. So I
advise not to stress too much about them.
> We don't need actually to freeze development,
Feature freeze is necessary for stabilization. It's what we do for every
release.
> Providing a release candidate and asking the community to test it would
We do that too.
> As for the next release being 2.0, I don't know. I would rather be
> careful and try to take little steps as I know everyone has a lot of
> expectations for 2.0
The plan is to start working on 2.0 as soon as 1.2 is out. And in fact
some of the work has already been started. I don't care really about
expectations... it's a necessary step in the evolution of LMMS, if you
want more detail you can read the mailing list archives where this has
been discussed in the past.
------------------------------------------------------------------------------
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
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
