Next release

2016-02-13 Thread Phil Holmes
Currently, lilypond.org is failing in its attempts to rsync data with 
linuxaudio.org.  That will mean that any new uploaded build will not be 
copied across to the download site, so we would announce the availability 
of the release on the lilypond.org website, but users would be unable to 
download it.

I've emailed Jan and Graham P to see if they can find out what's wrong: I 
don't believe I have enough knowledge or permission to debug the problem.  
I've had no response to date.

I'm therefore announcing that unless the problem is fixed, then there will 
be no build tomorrow and possibly for the foreseeable future.


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: PATCHES: Countdown for February 15th

2016-02-13 Thread James Lowe

Urs,

On 12/02/16 11:47, Urs Liska wrote:


Am 12. Februar 2016 12:41:30 MEZ, schrieb James :

Hello,

Here is the current patch countdown list. The next countdown will be on
February 15th.


...



4763 Web: Review GSoC page - Urs Liska
https://sourceforge.net/p/testlilyissues/issues/4763
http://codereview.appspot.com/285400043



Dies this need a full neqvreview cycle? I've just uploaded a new patch set with a minimal 
modification. The "review" was basically over,  and I suggest setting it to 
countdown immediately if it passes the tests. Or at least to review.

Urs




I have no feelings either way, there has been no objections, so if you 
think it doesn't need another 'review/countdown' cycle, then push it up 
to countdown. Make sure you add a note in the tracker so I can see it 
when I do the next cycle.



--
James

---

B8F4 5395 CBE2 ED37 7513 B075 FF32 5682 A84B D8BE


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: PATCHES: Countdown for February 15th

2016-02-13 Thread Urs Liska
Am 13.02.2016 um 14:16 schrieb James Lowe:
> Urs,
> 
> On 12/02/16 11:47, Urs Liska wrote:
>>
>> Am 12. Februar 2016 12:41:30 MEZ, schrieb James :
>>> Hello,
>>>
>>> Here is the current patch countdown list. The next countdown will be on
>>> February 15th.
>>>
>> ...
>>
>>>
>>> 4763 Web: Review GSoC page - Urs Liska
>>> https://sourceforge.net/p/testlilyissues/issues/4763
>>> http://codereview.appspot.com/285400043
>>>
>>>
>> Dies this need a full neqvreview cycle? I've just uploaded a new patch
>> set with a minimal modification. The "review" was basically over,  and
>> I suggest setting it to countdown immediately if it passes the tests.
>> Or at least to review.
>>
>> Urs
>>
>>
> 
> I have no feelings either way, there has been no objections, so if you
> think it doesn't need another 'review/countdown' cycle, then push it up
> to countdown. Make sure you add a note in the tracker so I can see it
> when I do the next cycle.

Thanks, I've done so (including a link to the latest delta).
Urs

> 
> 


-- 
Urs Liska
www.openlilylib.org

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Web: CSS: improve heading styles (issue 290790043 by paulwmor...@gmail.com)

2016-02-13 Thread paulwmorris

Reviewers: ,

Message:
Please review.  I've put up a demo copy of the full LilyPond website and
documentation with these CSS changes in effect, to make it easy to see
what they do.  (The changes only affect the various headings in the
manuals.)

Just remove the spaces in the following URL (which have been added here
to help thwart web crawlers/indexers (along with a robots.txt entry)).

http://clairnote.org  /lilypond-web-demo/



Description:
Web: CSS: improve heading styles

- Remove dashed bottom borders
- Adjust sizes and spacing
- Restore previous dark blue heading color
  from 2.18 web manuals

Please review this at https://codereview.appspot.com/290790043/

Affected files (+18, -16 lines):
  M Documentation/css/lilypond-manuals.css


Index: Documentation/css/lilypond-manuals.css
diff --git a/Documentation/css/lilypond-manuals.css  
b/Documentation/css/lilypond-manuals.css
index  
04a6877d8dbd833ba2568d7d5834ec3b6757ba29..cdbd6b76472ea8eeda00ee477ade4e2c44c69d25  
100644

--- a/Documentation/css/lilypond-manuals.css
+++ b/Documentation/css/lilypond-manuals.css
@@ -48,11 +48,10 @@ body {
 .appendix, .appendixsec, .appendixsubsec,
 .unnumbered, .unnumberedsec, .unnumberedsubsec, .unnumberedsubsubsec,
 .subheading, .subsubheading {
-  color: #black;
-  border-bottom: 1px dashed black;
+  color: rgb(32, 74, 135);
   padding-bottom: 0.15em;
   margin-top: 0.6em;
-  margin-bottom: 1em;
+  margin-bottom: 0.6em;
 }

 .settitle {
@@ -73,25 +72,28 @@ body.extending   .settitle { background-color: #7f4040;  
}

 body.internals   .settitle { background-color: #6a407f; }
 body.contributor .settitle { background-color: #00; }

-.chapter, .appendix, .unnumbered {
-  font-size: 1.8em;
-}
-
-.section, .appendixsec, .unnumberedsec {
-  font-size: 1.6em;
+.chapter, .appendix, .unnumbered,
+.section, .appendixsec, .unnumberedsec,
+.subsection, .appendixsubsec, .unnumberedsubsec,
+.subsubsection {
+  font-size: 1.7em;
+  margin-top: 0.9em;
 }

-.subsection, .appendixsubsec, .unnumberedsubsec {
-  font-size: 1.4em;
+.subheading, .unnumberedsubsubsec {
+  font-size: 1.5em;
+  margin-top: 0.9em;
 }

-.subheading, .subsubsection, .unnumberedsubsubsec {
-  font-size: 1.25em;
+.subheading {
+  border-top: 1px solid rgb(200, 200, 200);
+  padding-top: 0.8em;
 }

 .subsubheading {
-  font-size: 1em;
+  font-size: 1.15em;
   font-weight: bold;
+  margin-top: 1.6em;
 }

 .chapheading {
@@ -214,8 +216,8 @@ div#main ul {
 }

 h1, h2, h3, h4, p, table, address, dt {
-  padding-left: 1em;
-  padding-right: 1em;
+  padding-left: 18px;
+  padding-right: 18px;
 }

 p {



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel