@Stian
#1049 was marked for the 1.1 milestone on GitHub.
I know that complaining about known bugs doesn't help anything, but I
asked why this an some other bugs should be postponed further.
The only thing I wanted to say that I think it's better to focus on bug
fixing for 1.1 than releasing it without these fixes and work on new
features.
And I wasn't complaining about the speed of development or fixing, just
about the priorities.
(but probably my opinion is quite irrelevant since I don't pay them, so
I won't complain again..)
Am 23. Oktober 2014 14:20:58 MESZ, schrieb "Stian Jørgensrud"
<stian...@gmail.com>:
So #1049 have caused this for you since 1.0.0 and you are using 0.4.13/15?
And "why not" has been explained a lot of times, learn some C++ and you can
ask yourself :o :)
bubblegummer wrote
]Other 1.1 bugs that likely won't make the initial release:
]https://github.com/LMMS/lmms/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.1.0
Why not? Some of them are really annoying! #1049 makes half my
VSTs unusable, #1111 was introduced along all the new mixer
stuff. Everyone can try the new mixer etc in the RCs, so why
should introduce new bugs to master?
--
View this message in
context:http://linux-multimedia-studio-lmms.996328.n3.nabble.com/Let-s-release-1-1-tp10316p10654.html
Sent from the lmms-devel mailing list archive atNabble.com
<http://Nabble.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
