Re: Fwd: LilyPond Release Candidate for version 2.8

[Erik Sandberg]

On Tuesday 21 February 2006 19.23, Christian Hitz wrote:
> Sorry forgot the list.
>
> Anfang der weitergeleiteten E-Mail:
> > Am 17.02.2006 um 19:24 schrieb Han-Wen Nienhuys:
> >> By definition a bug is release critical if it wasn't present in
> >> version 2.6.
> >
> > Hi,
> >
> > in anticipation of the upcoming 2.8 release, I went through the
> > regression test document and compared the result of 2.7.35 to
> > 2.6.6. The following list contains those snippets, in which IMHO
> > 2.7.35 exhibits bugs not present in 2.6.6:

Thanks! I have went through the list, and confirmed some of the bugs.

> > accidental-tie.ly: tie collides with sharp sign

Happens in 2.6 as well, AFAICS. Also, I don't know if it's really a bug (how 
would you produce a tie without colliding with accidentals?).

I found a related (non-critical) bug though: Lily refuses to add an accidental 
to tied notes, even when ! is specified, and when ? is specified, some extra 
space is added: { cis~cis!~cis? }

> > ambitus.ly: no line between the notes of the ambitus

Agreed, critical bug.

> > auto-change.ly: additional staff

Not a critical bug, the error is in the .ly file: \new Staff should be changed 
to \context Staff. I fixed that.

> > beam-cross-staff-slope.ly: hairpin decrescendo collides with stems

Agreed, critical bug.

> > completion-heads-polyphony.ly: heads are not broken over barline

Can't reproduce.

> > mensural-ligatures.ly: no ligatures are printed

There's something strange here, but I don't understand mensural notation 
completely. I sent a mail to Juergen.

> > pedal-ped.ly: "Ped."  and "*" collide with notes

Agreed, critical bug.

> > phrasing-slur-slur-avoid.ly: PhrasingSlur collides with normal slurs

Agreed, critical bug.

> > ?repeat-line-break.ly: shouldn't the "2." volta bracket be open on
> > the right?

known critical bug (volta-bracket-break.ly). I added a note there.

> > tuplet-properties.ly: hte 7th tuplet still has a number

Error in the .ly file. I have corrected it (I think), using
  \override TupletNumber #'transparent = ##t

> > tuplet-rest.ly: strange 1st bracket

Agreed, critical bug.

> > volta-broken-left-edge.ly: closed continued volta brackets
The same known critical bug as the previous one, volta-bracket-break.


This leaves the following list of verified critical bugs:

> > ambitus.ly: no line between the notes of the ambitus
> > beam-cross-staff-slope.ly: hairpin decrescendo collides with stems
> > pedal-ped.ly: "Ped."  and "*" collide with notes
> > phrasing-slur-slur-avoid.ly: PhrasingSlur collides with normal slurs
> > tuplet-rest.ly: strange 1st bracket

Thanks,
-- 
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/bugs/v2.7/