> > > #1049 was marked for the 1.1 milestone on GitHub.
If you are going to try to make that point, please use it in context. This is what I wrote: > I'd like to mark this for 1.1 although I understand it might be a larger > undertaking to fix than the resources we have for 1.1. The fact that > users are claiming it broke somewhere along the line and the fact that the > bug is easily reproducible makes me inclined to say its worth putting on > the 1.1 radar.. Note the part about it being broken since a particular release was speculative and never proven with any use-case scenarios. The good part is, Toby self-assigned this which means he intends to help fix it. That's about as good as you are going to get with our tracker. Most bug reports don't get assigners, better yet Toby --- the one who wrote the software -- as the asignee. Furthermore, VSTs are proprietary plugins, so you have to understand that you won't get as much FOSS buy-in on these things. VSTs don't work at all on Mac and neither does a bunch of other important items. This bug is long standing and will be fixed when Toby (or someone else familiar with VST data storage) gets around to it, which is unlikely to happen for 1.1.0, but may happen for 1.1.x. -Tres - tres.finocchi...@gmail.com On Thu, Oct 23, 2014 at 12:52 PM, bubblegummer <bubblegumm...@gmail.com> wrote: > @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> <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 at Nabble.com. >> >> ------------------------------ >> ------------------------------ >> >> LMMS-devel mailing >> listLMMS-devel@lists.sourceforge.nethttps://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
