[svn:parrot] r42601 - trunk/docs

[jkeenan at svn.parrot.org]

Author: jkeenan
Date: Fri Nov 20 16:10:01 2009
New Revision: 42601
URL: https://trac.parrot.org/parrot/changeset/42601

Log:
Make explicit that new configuration steps should be proposed via Trac ticket.

Modified:
   trunk/docs/configuration.pod

Modified: trunk/docs/configuration.pod
==============================================================================
--- trunk/docs/configuration.pod	Fri Nov 20 14:45:33 2009	(r42600)
+++ trunk/docs/configuration.pod	Fri Nov 20 16:10:01 2009	(r42601)
@@ -26,7 +26,9 @@
 example, if you added a new user-configurable type called C<FOOVAL>, you would
 add the code used to determine its size in F<config/auto/sizes.pm>.  However,
 if you were determining what dynaloading capabilities are available, you would
-create a new step.
+create a new step.  It is strongly recommended that you file a Trac ticket in
+which you state the rationale for adding a new configuration step and sketch
+out what the code in the step would look like.
 
 =head2 Initialization Steps
 
@@ -57,9 +59,10 @@
 
 =head2 Generations
 
-Generations create files needed after configuration has completed, such as
-Makefiles and configuration headers. A step containing generations is a
-I<generation step>. Generation steps should be in the F<config/gen> folder.
+Generations create files which will be needed once configuration has
+completed, such as Makefiles and configuration headers. A step containing
+generations is a I<generation step>. Generation steps should be in the
+F<config/gen> folder.
 
 Templates for files to be generated usually have the extension F<.in>.  There
 are variable substitutes and funny macros like C<#IF> and C<#UNLESS>