Re: Staging->Master

Reinhold Kainhofer writes: > On 2012-02-02 18:11, Phil Holmes wrote: >> - Original Message - From: "David Kastrup" >> To: "Phil Holmes" >>> I believe James indicated his big machine was on 24x7 - hence my instructions if he has some time to look at this. >>> >>> I think that t

Re: Staging->Master

David Kastrup writes: > Reinhold Kainhofer writes: > >> On 2012-02-02 18:11, Phil Holmes wrote: >>> - Original Message - From: "David Kastrup" >>> To: "Phil Holmes" > I believe James indicated his big machine was on 24x7 - hence my > instructions if he has some time to loo

Roadblock MacOSX 10.4 for release of LilyPond 2.16

Hi, in the list of critical issues the recent issue 2271 http://code.google.com/p/lilypond/issues/detail?id=2271> is the only one I see without an obvious path forward. One serious option is ending the support for MacOSX 10.4. If you are a user that would be affected by such a step, or a develo

Re: Staging->Master

2012/2/3 David Kastrup : > Since I just pushed about 4 patches (2 of them from me) and there has > been another translation merge (they tend to be prone to surprises in > particular when we have syntax changes), Dear David: of course. What else do you expect? I'd rather say: merging master into t

Re: Staging->Master

Francisco Vila writes: > 2012/2/3 David Kastrup : >> Since I just pushed about 4 patches (2 of them from me) and there has >> been another translation merge (they tend to be prone to surprises in >> particular when we have syntax changes), > > Dear David: of course. What else do you expect? What

Re: Staging->Master

2012/2/3 David Kastrup : > It looked like there were a lot of changes in Italian.  And many of the > changes we actually had problems with were trivial.  makeinfo does not > care much about the complexity of problems it complains about. I meant "trivial" as in "absolutely no problem giving" -- F

Re: Staging->Master

Francisco Vila writes: > 2012/2/3 David Kastrup : >> It looked like there were a lot of changes in Italian.  And many of the >> changes we actually had problems with were trivial.  makeinfo does not >> care much about the complexity of problems it complains about. > > I meant "trivial" as in "abs

issues to verify -> no more releases

Now that the Patchy staging-merge is running ok, it's time to force the next issue: I will not be making any more releases, stable or unstable, as long as there are issues to verify relating to a previously-released version. At the time of this writing, this means that if *ANY* issue on this

Re: Roadblock MacOSX 10.4 for release of LilyPond 2.16

On Fri, Feb 03, 2012 at 11:56:06AM +0100, David Kastrup wrote: > > in the list of critical issues the recent issue 2271 > http://code.google.com/p/lilypond/issues/detail?id=2271> is the > only one I see without an obvious path forward. A quick glance at http://code.google.com/p/lilypond/issues/de

Re: issues to verify -> no more releases

On Fri, Feb 03, 2012 at 01:14:52PM +0100, David Kastrup wrote: > Graham Percival writes: > > > At the time of this writing, this means that if *ANY* issue on this > > list: > > http://code.google.com/p/lilypond/issues/list?can=7 > > does *NOT* say "fixed_2_15_28", there will be no release. > > "

Re: issues to verify -> no more releases

Graham Percival writes: > On Fri, Feb 03, 2012 at 01:14:52PM +0100, David Kastrup wrote: >> Graham Percival writes: >> >> > At the time of this writing, this means that if *ANY* issue on this >> > list: >> > http://code.google.com/p/lilypond/issues/list?can=7 >> > does *NOT* say "fixed_2_15_28"

Re: issues to verify -> no more releases

On Fri, Feb 03, 2012 at 02:14:41PM +0100, David Kastrup wrote: > Graham Percival writes: > > > Programmers gives things fixed_* tags. > > You wish. Heh. Normative vs. descriptive. :) Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@

Re: issues to verify -> no more releases

On Fri, Feb 03, 2012 at 01:14:52PM +0100, David Kastrup wrote: > Graham Percival writes: > > At the time of this writing, this means that if *ANY* issue on this > > list: > > http://code.google.com/p/lilypond/issues/list?can=7 > > does *NOT* say "fixed_2_15_28", there will be no release. > > "ve

Re: issues to verify -> no more releases

On Fri, Feb 03, 2012 at 01:40:49PM +, Colin Hall wrote: > > Looks like Dave has marked all the outstanding fixes as verified while I was > busy testing 1416. almost; there's still 2149. > My understanding is that they still all need to be tested. I'm travelling > from Saturday but I'll try

Re: issues to verify -> no more releases

Graham Percival writes: > On Fri, Feb 03, 2012 at 01:40:49PM +, Colin Hall wrote: >> >> Looks like Dave has marked all the outstanding fixes as verified >> while I was busy testing 1416. > > almost; there's still 2149. You could have stowed the whip for a few minutes. There is a new patch

Re: issues to verify -> no more releases

On Fri, Feb 03, 2012 at 01:45:26PM +, Graham Percival wrote: > On Fri, Feb 03, 2012 at 01:40:49PM +, Colin Hall wrote: > > > My understanding is that they still all need to be tested. I'm travelling > > from Saturday but I'll try to get through as many as I can between now and > > then.

Re: PATCH: Countdown to 20120205

On 12-02-02 11:45 PM, m...@apollinemike.com wrote: On Feb 3, 2012, at 6:14 AM, Colin Campbell wrote: For 20:00 MST Sunday February 5th, 2012 Critical: Issue 2267 : Patch: Gets left Hairpin bounds correct with tempo indications - R

Re: issues to verify -> no more releases

Colin Hall writes: > On Fri, Feb 03, 2012 at 01:45:26PM +, Graham Percival wrote: >> On Fri, Feb 03, 2012 at 01:40:49PM +, Colin Hall wrote: >> >> > My understanding is that they still all need to be tested. I'm >> > travelling from Saturday but I'll try to get through as many as I >> >

Re: Doc: simplify example for unpure-pure containers (issue 5623044)

To be honest, there are many things I don't understand. In fact, I reduced the example to understand it better. Why is horizontal spacing affected even though the purity affects the Y-axis only? Why do stems fix the spacing? Why doesn't this cause the spacing problem: \override NoteHead #'t

Another stderr/stdout question

The regtest option-help.ly emits the help text for ly:set-option. The idea is that the logfiles will thus be compared in the regtest checking. Only problem is that the list seems to go to stdout and the logfiles are produced from stderr, so no checking actually occurs, AFAICS. This has the si

Re: Another stderr/stdout question

"Phil Holmes" writes: > The regtest option-help.ly emits the help text for ly:set-option. The > idea is that the logfiles will thus be compared in the regtest > checking. Only problem is that the list seems to go to stdout and the > logfiles are produced from stderr, so no checking actually occ

Re: Another stderr/stdout question

- Original Message - From: "David Kastrup" To: Sent: Friday, February 03, 2012 5:20 PM Subject: Re: Another stderr/stdout question "Phil Holmes" writes: The regtest option-help.ly emits the help text for ly:set-option. The idea is that the logfiles will thus be compared in the re

failure rewriting Patchy

Dear developers, i hoped to rewrite Patchy to make it more robust, user-friendly and solve problems that David experienced with his fix for 2240; unfortunately it turned out that i'm not experienced enough to do this. After 50 hours of struggle i'm so frustrated that i cannot continue. I'm sorry

Re: failure rewriting Patchy

2012/2/4 Janek Warchoł : > PS despite how this turned out, i'd like to thank Julien and Mike for > their help. And, of course, Carl. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel