Log Message:
-----------
Fix sgml errors

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        adminscripts.sgml (r1.44 -> r1.45)
        releasechecklist.sgml (r1.7 -> r1.8)

-------------- next part --------------
Index: adminscripts.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/adminscripts.sgml,v
retrieving revision 1.44
retrieving revision 1.45
diff -Ldoc/adminguide/adminscripts.sgml -Ldoc/adminguide/adminscripts.sgml -u -w -r1.44 -r1.45
--- doc/adminguide/adminscripts.sgml
+++ doc/adminguide/adminscripts.sgml
@@ -534,6 +534,7 @@
 environment variables, you will get a set of slonik scripts.  They may
 not correspond, of course, to any database you actually want to
 use...</para>
+</sect3>
 
 <sect3><title>Node-Specific Values</title>
 
Index: releasechecklist.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/releasechecklist.sgml,v
retrieving revision 1.7
retrieving revision 1.8
diff -Ldoc/adminguide/releasechecklist.sgml -Ldoc/adminguide/releasechecklist.sgml -u -w -r1.7 -r1.8
--- doc/adminguide/releasechecklist.sgml
+++ doc/adminguide/releasechecklist.sgml
@@ -8,28 +8,23 @@
 
   <listitem><para>Positive build reports for each supported platform -
   although it is arguably less necessary for a comprehensive list if
-  we are releasing a minor upgrade
+  we are releasing a minor upgrade </para></listitem> 
 
-  </para></listitem> 
-
-<listitem><para>Some kind of Standard Test Plan 
-
-  </para></listitem> 
-<listitem><para>Binary RPM packages 
+<listitem><para>Some kind of Standard Test Plan</para></listitem> 
+<listitem><para>Binary RPM packages</para></listitem> 
 
-  </para></listitem> 
-
-<listitem><para>If the release is a <quote>.0</quote> one, we need to
+<listitem>
+ <para>If the release is a <quote>.0</quote> one, we need to
 open a new STABLE branch</para>
 
-<para> <command> cvs tag -b REL_1_2_STABLE</command>
-
-<listitem><para>Tag the with the release ID. For version 1.1.2, this
+ <para> <command> cvs tag -b REL_1_2_STABLE</command></para>
+</listitem>
+<listitem>
+ <para>Tag the with the release ID. For version 1.1.2, this
 would be <envar>REL_1_1_2 </envar></para>
 
-<para> <command> cvs tag REL_1_1_2 </command>
-
-</para></listitem> 
+ <para> <command> cvs tag REL_1_1_2 </command></para>
+</listitem> 
 
 <listitem><para>Check out a copy via <command>cvs export -rREL_1_1_2 </command>
 
@@ -48,16 +43,15 @@
 <para> This does a bunch of consistency checks to make sure that
 various files that are supposed to contain version numbers contain
 consistent values.</para> 
+</listitem>
+<listitem><para>For instance, configure should contain, for release 1.1.2:</para></listitem>
 
-<itemizedlist>
-<listitem><para>For instance, configure should contain, for release 1.1.2:</para>
-<itemizedlist>
 <listitem><para>PACKAGE_VERSION=REL_1_1_2</para></listitem>
 
 <listitem><para>PACKAGE_STRING=postgresql-slony1-engine REL_1_1_2</para></listitem>
 
-</itemizedlist></listitem>
-
+</itemizedlist>
+<itemizedlist>
 <listitem><para> <filename> config.h.in </filename> needs to contain the version
 number in two forms; the definitions for
 <envar>SLONY_I_VERSION_STRING</envar> and
@@ -71,20 +65,12 @@
 <function>slonyVersionPatchlevel()</function>.  These need to be
 assigned <quote>by hand</quote> at this point.</para> </listitem>
 
-<para> It sure would be nice if more of these could be assigned
+<listitem><para> It sure would be nice if more of these could be assigned
 automatically, somehow.</para>
 
 <para><emphasis>Don't</emphasis> commit the new
 <filename>configure</filename>; we shouldn't be tracking this in CVS.
-</para>
-
-<listitem><para> One test that seems inherently troublesome to
-automate is the set of version numbers listed in upgradeSchema() in
-src/backend/slony1_funcs.sql. </para>
-
-<para> As new versions are released, the lists of version numbers will
-need to get changed; this does not seem amenable to much
-automation. </para> </listitem>
+</para></listitem>
 
 <listitem><para>make sure that the generated files from .l and .y are
 created, for example <filename>slony/conf-file.[ch]</filename> </para>