[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.6 release. (Was: new manual chapter)

From: Alexander Strasser
Subject: Re: 2.6 release. (Was: new manual chapter)
Date: Wed, 4 May 2005 12:02:54 +0200
User-agent: Mutt/1.5.6+20040907i


Han-Wen Nienhuys wrote:
> Graham Percival wrote:
> >
> >>  The basic problem with complex examples, is that they're
> >>difficult to read if you don't already know what they say.
> >
> >
> >I confess that I haven't completely thought out what to do with this
> >new possible chapter.  I'm pretty sure that we could use another
> >wordy chapter that explains some of the more complicated lilypond
> >stuff; I'm not certain whether that should take the form of annotated
> >short examples, annotated complicated contrived examples, or just
> >an extension of the existing tutorial (but in a separate chapter for
> >ease of reading).
> >
> >If we're going to have a new chapter, IMO it should be included before
> >2.6.0.  We've rearranged the manual between 2.4 and 2.6, so users will
> >have to get used to a new chapter numbering scheme; it would be a pity
> >if 2.6.5 (or whatever) introduced a new chapter which changed the
> >chapter numbering scheme again.
> In general, I advise to resist the temptation to start something new 
> (new chapter, new approaches), until you're sure that what we have 
> doesn't work. Starting something new is easy, but following through with 
> something isn't.
> Regarding the release: you can insert an empty chapter now. I hope to 
> release 2.6 Real Soon Now, and I don't want to stop the release because 
> of unwritten doc chapters.

  Just wanted to note that as a lilypond user i find Graham's idea very
good. Also some time passed already since i last used lilypond, i still
remember very clearly that i had big problems getting the pieces together
to form a bigger picture of how my typical lily source file should look

  Release of course is different problem, and i don't want to say anything
about that as you should know best about that topic. I only wanted to
give feedback as it can be useful for developers (documentation writers
are also devels in my oppinion).

  Alex (beastd)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]