New features vs bug fix
ustk last edited by ustk
@Christoph-Hart I know you are a very busy professional man, but would it be possible to get old stuff fixed before adding new things? I'm happy to see them arriving of course, but I'm sure Hise could gain a lot from having a fewer bugs to drag behind.
orange last edited by orange
Definitely Agree. Before the new implementations, it would be awesome to see the finished scriptnode branch release!
Christoph Hart last edited by
@ustk I'm currently preparing a release so naturally there will be lots of bug fixes when it's in the beta phase a few weeks from now (it also utilizes scriptnode), and any new feature (like the copy protection I pushed today) is a just side-product of the things I need to implement anyway.
Also I have done lots of bug fixes and stability improvements in the last two months (including a regression test framework for scriptnode), so while I generally understand that argument (and @Fortune complained about that before it was cool), it's not 100% accurate for the current phase.
d.healey last edited by
@christoph-hart Has any further progression been made with implementing a bug tracking solution? I remember a while ago we were talking about it and said it might be something Dominik could work on.
ustk last edited by
@christoph-hart That is very comforting indeed. It is just that if you already have taken into account some preceding bugs, we don't know. So they might just be lost in the forum until they rise again. Definitely, a bug tracking solution would be nice for us like for you I think.
iamlamprey last edited by iamlamprey
quick +1 for a bug tracker because I still need help getting convolution to not look inside expansions since it's the last thing preventing my mac release