Re: Backporting / stable

2011-05-03 Thread Phil Holmes
- Original Message - From: Trevor Daniels t.dani...@treda.co.uk To: Carl Sorensen c_soren...@byu.edu; Lily devel lilypond-devel@gnu.org Sent: Sunday, May 01, 2011 9:20 AM Subject: Re: Backporting / stable Carl Sorensen wrote Saturday, April 30, 2011 1:59 PM So it appears

Re: Backporting / stable

2011-05-03 Thread Graham Percival
On Tue, May 03, 2011 at 11:52:01AM +0100, Phil Holmes wrote: Slightly related to this - if a bug is marked fixed 2.15.0 backport, should it also have a 2.13 version number for the claim fix? No. (well, Carl will add a 2.13 version number -- but that is something that Carl, and only Carl,

Re: Backporting / stable

2011-05-01 Thread Trevor Daniels
Carl Sorensen wrote Saturday, April 30, 2011 1:59 PM So it appears that the biggest source of Critical bugs, and the thing that is holding up release of 2.14, is the beam-collision-engraver. Should we try to remove the beam-collision-engraver from 2.14.0? Or should we wait for it to settle

Backporting / stable

2011-04-30 Thread Carl Sorensen
So it appears that the biggest source of Critical bugs, and the thing that is holding up release of 2.14, is the beam-collision-engraver. Should we try to remove the beam-collision-engraver from 2.14.0? Or should we wait for it to settle itself out and make it part of 2.14.0? I can see

Re: Backporting / stable

2011-04-30 Thread Phil Holmes
- Original Message - From: Carl Sorensen c_soren...@byu.edu To: Lily devel lilypond-devel@gnu.org Sent: Saturday, April 30, 2011 1:59 PM Subject: Backporting / stable So it appears that the biggest source of Critical bugs, and the thing that is holding up release of 2.14, is the beam

Re: Backporting / stable

2011-04-30 Thread Carl Sorensen
On 4/30/11 8:07 AM, Phil Holmes m...@philholmes.net wrote: - Original Message - From: Carl Sorensen c_soren...@byu.edu To: Lily devel lilypond-devel@gnu.org Sent: Saturday, April 30, 2011 1:59 PM Subject: Backporting / stable So it appears that the biggest source of Critical

Re: Backporting / stable

2011-04-30 Thread Graham Percival
On Sat, Apr 30, 2011 at 08:37:01AM -0600, Carl Sorensen wrote: I actually think it would be more work to remove the beam-collision-engraver than to keep it in. But at this point I expect it to be months before we are sure we're clear of Critical bugs in beam-collision engraver. We don't

Re: Backporting / stable

2011-04-30 Thread Carl Sorensen
On 4/30/11 8:49 AM, Graham Percival gra...@percival-music.ca wrote: On Sat, Apr 30, 2011 at 08:37:01AM -0600, Carl Sorensen wrote: I actually think it would be more work to remove the beam-collision-engraver than to keep it in. But at this point I expect it to be months before we are sure

Re: Backporting / stable

2011-04-30 Thread Graham Percival
On Sat, Apr 30, 2011 at 08:52:42AM -0600, Carl Sorensen wrote: On 4/30/11 8:49 AM, Graham Percival gra...@percival-music.ca wrote: We don't need to be sure that we're clear. All we need... or at least, all I want before uploading the official 2.14.0... is for one week without *known*

Re: Backporting / stable

2011-04-30 Thread m...@apollinemike.com
On Apr 30, 2011, at 8:03 AM, Graham Percival wrote: On Sat, Apr 30, 2011 at 08:52:42AM -0600, Carl Sorensen wrote: On 4/30/11 8:49 AM, Graham Percival gra...@percival-music.ca wrote: We don't need to be sure that we're clear. All we need... or at least, all I want before uploading the

Re: Backporting / stable

2011-04-30 Thread Carl Sorensen
On 4/30/11 4:51 PM, m...@apollinemike.com m...@apollinemike.com wrote: On Apr 30, 2011, at 8:03 AM, Graham Percival wrote: On Sat, Apr 30, 2011 at 08:52:42AM -0600, Carl Sorensen wrote: On 4/30/11 8:49 AM, Graham Percival gra...@percival-music.ca wrote: We don't need to be sure that we're