Rodrigo Vilar

@ryanclark @codymikol when it is planned to make the next release? The problems we have in OSMD are already resolved in the current code base.

> @rvilarl Do you remember why you added the null checks for gve.parentVoiceEntry? Like some occurences of `graphicalVoiceEntry.parentVoiceEntry` to `graphicalVoiceEntry.parentVoiceEntry?`? I don't think parentVoiceEntry can ever be undefined. E.g. in...

@sschmidTU could you raise a PR in vexflow with test cases showing the problems above?

> > @sschmidTU could you raise a PR in vexflow with test cases showing the problems above? > > @rvilarl You mean an issue? Or 16 PRs (for the 16...

> * [ ] Rests too cramped in OSMD Function Test - Multiple Rest Measures (rather minor issue) >  @sschmidTU I found out that the web demo does it...

> @rvilarl Not sure if I understand you correctly, but the web demo does it correctly because it's using vexflow 1.2.93. In the visual regression, only `current` (vexflow 4) does...

> edit: oh, you mean the localhost debug demo? hmm, sometimes there are some slight differences in the visual regression tests, but they shouldn't be this big. would need investigating...

These two are also fixed (even in visual regressions), please mark them as resolved:  

> * [ ] Unnecessary x-shift from note alignment in test_note_alignment_long_distance > * [ ] Collision of section mark and box not removable anymore in test_rehearsal_marks_bolivia > * [ ]...

@sschmidTU could you resolve the merge issue? And also one question, which issues are a 'must' to get this finally integrated into develop? I ask because there is one marked...