Hi Tim! 22.10.2015 04:14, Tim E. Real пишет: > On October 12, 2015 03:52:56 PM Andrew Deryabin wrote: >> Hi Robert, >> >> 12.10.2015 13:27, Robert Jonsson пишет: >>> Hi Andrew, >>> >>> I see you are fixing stuff so I just wanted to comment that although I >>> feel I should do more, the current master seems to be pretty good. So >>> maybe it's time to start preparing for a release then? :) >> I completely agree about new release. I wanted to make it before a new >> year :). Now the only thing that should be done before is to make some >> more tests of new cpu measure code - it's now free of jack api and >> calculates cpu usage only by means of system calls to kernel time functions. >>> Regards, >>> Robert >>> >>> ps. >>> The limited testing I have done I DID get some crashes (I think when >>> opening plugin guis, not sure if it was VST or LV2) so if I find the >>> time again I will run MusE under gdb or make sure there are crash >>> dumps so maybe I can catch the problem. >>> ds. >> Ok! I also should write a new demo song to mark this new release :). May >> be this can help to find and fix some more bugs. > > Hey! > Thanks for working overtime helping all the users and new devs! > > Must chime in here... > > Would you guys mind if merged my code from my > persistent_routes branch to master soon, before release? > > After one year, this code is not going away and I cannot abandon it. > It is NOT finished and has a few rough edges, but it is almost done, > mostly functional, and crucially contains the long awaited addition > of being able to remove those persistent routes that the user adds. > > If we release master now, the persistent routes code that I merged > about a year ago is in there - but without a way to remove those routes. > So I'm worried that users may find a bunch of routes they can't remove. > However, that is not terribly serious, the routes will simply be there > until I merge this latest code and we release again. > Plus, there are several /seriously/ significant changes in this new code. > However, if I merge now, given a month or so of testing by all of us, > it should be fine. > > It is probably best that I get this new code into master soon before > someone else does a major merge and I'm left in the dust, > and so other devs can get used to this new code. > > Kinda tricky, but if you want to wait a bit, this release will be a good one. > Up to you... should I merge? It really /must/ be done, sooner or later... Your persistent routes can make life much easier, really :). When I last tested it, I was able to replug usb midi keyboard at any time and get it connected instantly. So, as for me, I'm completely sure, that new changes *should* be merged to master before new release! And I'll be a tester, of course. > > I can give much more details about what has been done if you like. > > Thanks! > Tim.
-- Regards, Andrew ------------------------------------------------------------------------------ _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
