CG: clarify doc suggestions to mailing list.

[lilypond.git] / Documentation / contributor / administration.itexi

diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi
index 8dbc9eb68ffbdb1f5fa99ab897ab7613ee1e59c2..e906dc362c3dfdf73f15569f9d4061bdeadc56dd 100644 (file)
--- a/Documentation/contributor/administration.itexi
+++ b/Documentation/contributor/administration.itexi
@@ -347,7 +347,7 @@ discussion.
 
 @warning{The estimated time required for "prep work", and the
 following discussion, has been added to each item.  At the moment,
 
 @warning{The estimated time required for "prep work", and the
 following discussion, has been added to each item.  At the moment,

-there is an estimated 30 hours of prep work and 135 hours of
+there is an estimated 30 hours of prep work and 140 hours of

 discussion.}
 
 @itemize
 discussion.}
 
 @itemize


@@ -485,6 +485,28 @@ required merging and stuff.
 
 (prep: 2 hours.  discuss: 10 hours)
 
 
 (prep: 2 hours.  discuss: 10 hours)
 

+@item @strong{Precise definition of Critical issues}:
+at the moment, a stable release is entirely dependent on the
+number of Critical issues, but there's some questions about
+precisely what a "Critical issue" should be.  We should clarify
+this, in conjunction with a general discussion about how often we
+want to have stable releases, how permissive we want to be about
+patches, etc etc.
+
+(prep: 1 hour.  discuss: 5 hours)
+
+@item @strong{When do we add regtests?}:
+There is a discrepancy between our stated policy on adding
+regtests, and our actual practice in handling bugs and patches.
+Clarify.
+
+There is also a wider question how to organize the regtests, such
+as where to put interesting-console-output regtests, including
+stuff like lilypond-book and midi2ly in a sensible manner, and
+possibly including regtests for currently-broken functionality.
+
+(prep: 2 hours.  discuss: 5 hours)
+

 @end itemize
 
 
 @end itemize
 
 


@@ -830,62 +852,3 @@ developers are tired of pushing patches for a contributor, we'll
 discuss giving them push access.  Unsolicited requests from
 contributors for access will almost always be turned down.
 
 discuss giving them push access.  Unsolicited requests from
 contributors for access will almost always be turned down.
 

-
-@subsubheading Creating the @strong{Lilydev} respin
-
-@enumerate
-
-@item Install ubuntu, reboot
-
-@item Run all updates, reboot if asked
-
-@item Enable src repos, refresh package lists
-
-@item install LP build deps:
-
-@example
-sudo apt-get build-dep lilypond
-@end example
-
-@ install git and other stray build dependencies:
-
-@example
-sudo apt-get install git-core gitk autoconf dblatex
-@end example
-
-@item TEST TO SEE WHETHER EVERYTHING WORKS NOW:
-
-@itemize
-
-@item use @code{lily-git.tcl} to grab source files
-@item go to source directory and do @code{./autogen.sh ;
-make all ; make doc}
-
-@item if all compiles, move on to iso creation...
-
-@end itemize
-
-@item Download & install "remastersys" package:
-
-@example
-@uref{http://sourceforge.net/projects/remastersys/}
-@end example
-
-@item copy @code{lily-git.tcl} script file into @code{/etc/skel/}
-
-@item modify @code{/etc/remastersys.conf} as desired
-(change .iso name, default live session username, etc)
-
-@item Remove non-essential desktop software as desired
-@item create iso:
-
-@example
-sudo remastersys dist
-@end example
-
-@item new iso is in @code{/home/remastersys/remastersys/}
-
-@item test iso by installing in VM and repeating steps above for
-getting source files and building lp and docs
-
-@end enumerate