patch::: 1.3.138.jcn1

[lilypond.git] / README.txt

diff --git a/README.txt b/README.txt
index b254f58698b253a79af6926ba693f94abf0fd2c1..c07974d42cf537de68757b2bd993bac75164002e 100644 (file)
--- a/README.txt
+++ b/README.txt
@@ -12,9 +12,13 @@ Versioning
 
    LilyPond uses a versioning scheme similar to the Linux kernel.  In a
 version "x.y.z", an even second number 'y' denotes a stable version.
-For development versions 'y' is odd.  For using straightforward score
-production, please use the latest stable version.  Development versions
-may not produce good or nice scores.
+For development versions 'y' is odd.  So, in theory, version 1.2 is
+stable, which means that there are no glaring errors in it. In practice
+1.2.x is also unmaintained.
+
+   1.3.x is in healthy development: lots of problems turn up, but
+they're fixed quickly. Therefore we recommend you try 1.2.x, if you
+have any problem with it, upgrade to the latest 1.3.x release.
 
 Requirements
 ============
@@ -22,8 +26,8 @@ Requirements
    For the compilation and running of LilyPond you need some additional
 packages.  Please refer to the installation instructions.
 
-   NOTE: If you downloaded a binary (.rpm or a W95/NT .zip file), then
-you don't have to compile LilyPond.
+   NOTE: If you downloaded a binary (.rpm or a W95/NT .zip file), you
+don't have to compile LilyPond.
 
 Installation
 ============
@@ -37,36 +41,52 @@ Documentation
    The real documentation is the directory Documentation/
 
    If you want to read the documentation online, these are options:
-   * use `.html'. Refer to INSTALL.txt for info on how to make the
-     .html documentation.
+   * use HTML. Refer to INSTALL.txt for information on how to make the
+     HTML documentation.
 
-   * use `.html'. Point your browser to
+   * use HTML. Point your browser to
      `http://www.cs.uu.nl/~hanwen/lilypond/index.html'.
 
    * use `.dvi',  for the tutorial and reference manual. Do
 
-            make -C Documentation/tex/ dvi
+            make -C Documentation/user/ dvi
+
+     You need a working LilyPond binary to create the DVI and HTML
+     sources.
 
    * use ASCII. Do using
-               make -C Documentation/
+               make doc
 
 
 Comments
 ========
 
    LilyPond is a long way from finished and polished.  We do appreciate
-criticism, comments, bugreports, patches, etc.
+criticism, comments, bugreports, patches, etc., but please,
 
           Please send your e-mail to one of the MAILING LISTS
 
-   and _not_ to us personally.  See `Documentation/mail.texi' for more
-info.
+   and _not_ to us personally. We have the following mailing lists:
+
+   * info-gnu-music@gnu.org
+     (http://mail.gnu.org/mailman/listinfo/info-gnu-music) is a
+     low-volume list for information on the GNU Music project.
+     This list is moderated; ask     David R. Linn <drl@gnu.org> or
+     Han-Wen <hanwen@cs.uu.nl> to send announcements for this list.
+
+   * help-gnu-music@gnu.org
+     (http://mail.gnu.org/mailman/listinfo/help-gnu-music)     For help
+     with using LilyPond.
+
+   * bug-gnu-music@gnu.org
+     (http://mail.gnu.org/mailman/listinfo/bug-gnu-music) If you have
+     bugreports, you should send them to this list.
 
 Windows 32
 ==========
 
    If you have received this file as part of a DOS/Window32 distribution
-(`LilyPond-*.zip'), then it is advisable to also download the source
+(`LilyPond-*.zip'), it is advisable to also download the source
 package, since it might contain more documentation
 `ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/'
 
@@ -90,10 +110,3 @@ use <help-gnu-music@gnu.org> and <gnu-music-discuss@gnu.org>.  Please
 consult the FAQ and installation instructions before mailing your
 problems.
 
-CDROM distributions
-===================
-
-   if you have received LilyPond on a cdrom, chances are that
-development has moved a some patchlevels up.  Please check the latest
-version of LilyPond before reporting bugs.
-