Log Message:
-----------
Add more steps to the release checklist

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        releasechecklist.sgml (r1.3 -> r1.4)

-------------- next part --------------
Index: releasechecklist.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/releasechecklist.sgml,v
retrieving revision 1.3
retrieving revision 1.4
diff -Ldoc/adminguide/releasechecklist.sgml -Ldoc/adminguide/releasechecklist.sgml -u -w -r1.3 -r1.4
--- doc/adminguide/releasechecklist.sgml
+++ doc/adminguide/releasechecklist.sgml
@@ -18,9 +18,19 @@
 <listitem><para>Binary RPM packages 
 
   </para></listitem> 
-<listitem><para>Tag with the release ID. For version 1.1.2, this would be <envar>REL_1_1_2 </envar>
+
+<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
+would be <envar>REL_1_1_2 </envar></para>
+
+<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>
 
   </para></listitem> 
@@ -43,13 +53,16 @@
 
 <para> RPM spec files used to contain release tags as well as names of tarballs which needed to be updated. As of 2005-12-13, there is less of this...   For those platforms with specific spec files such as SuSE, some editing still needs to be done. see the file(s) in the <filename>suse</filename> dir for more information </para>
 
-<para> The admin guide <filename>version.sgml</filename> file needs to contain the release name. This should not need to be touched; version.sgml is generated automatically with the release name/tag on demand. </para>
+<para> The admin guide <filename>version.sgml</filename> file needs to
+contain the release name. This should not need to be touched;
+<filename>version.sgml</filename> is generated automatically with the
+release name/tag on demand. </para>
 
 <para> It sure would be nice if more of these could be assigned automatically, somehow.
 
 </para></listitem> 
-<listitem><para>commit the new configure 
 
+<listitem><para><emphasis>Don't</emphasis> commit the new configure.
   </para></listitem> 
 
 <listitem><para>make sure that the generated files from .l and .y are
@@ -59,27 +72,44 @@
 make all && make clean</command> but that is a somewhat ugly approach.
 
 </para></listitem> 
-<listitem><para>Generate HTML tarball, and RTF/PDF, if possible... Note that the HTML version should include *.html (duh!), *.jpg, *.png, as well as *.css 
-  </para></listitem> 
 
-<listitem><para>Run <command>make clean</command> in <filename>doc/adminguide</filename> before generating the tarball in order that <filename>bookindex.sgml</filename> is NOT part of the tarball 
+<listitem><para> Make sure that generated Makefiles and such from the
+previous step(s) are removed.</para>
 
-  </para></listitem> 
-<listitem><para>Alternatively, delete <filename>doc/adminguide/bookindex.sgml </filename>
+<para> <command>make distclean</command> ought to do
+that... </para></listitem>
 
-  </para></listitem> 
-<listitem><para>Rename the directory (e.g <filename>slony1-engine</filename>) to a name based on the release, e.g. - <filename>slony1-1.1.2 </filename>
+<listitem><para>Generate HTML tarball, and RTF/PDF, if
+possible... Note that the HTML version should include *.html (duh!),
+*.jpg, *.png, as well as *.css </para></listitem>
 
-  </para></listitem> 
-<listitem><para>Generate a tarball - <command>tar tfvj slony1-1.1.2.tar.bz2 slony1-1.1.2 </command>
+<listitem><para>Run <command>make clean</command> in
+<filename>doc/adminguide</filename> before generating the tarball in
+order that <filename>bookindex.sgml</filename> is NOT part of the
+tarball </para></listitem>
 
+<listitem><para>Alternatively, delete
+<filename>doc/adminguide/bookindex.sgml </filename> </para></listitem>
+
+<listitem><para>Rename the directory (<emphasis>e.g.</emphasis> -
+<filename>slony1-engine</filename>) to a name based on the release,
+<emphasis>e.g.</emphasis> - <filename>slony1-1.1.2</filename>
   </para></listitem> 
-<listitem><para>Build the administrative documentation, and build a tarball as <filename>slony1-1.1.2-html.tar.bz2</filename></para>
- <para> Make sure that the docs are inside a subdir in the tarball.
 
+<listitem><para>Generate a tarball - <command>tar tfvj
+slony1-1.1.2.tar.bz2 slony1-1.1.2 </command> </para></listitem>
+
+<listitem><para>Build the administrative documentation, and build a
+tarball as <filename>slony1-1.1.2-html.tar.bz2</filename></para>
+
+<para> Make sure that the docs are inside a subdir in the tarball.
 </para></listitem> 
-<listitem><para>Put these tarballs in a temporary area, and notify everyone (on some mailing list???) that they should test them out ASAP based on the Standard Test Plan. 
-</para></listitem></itemizedlist>
+
+<listitem><para>Put these tarballs in a temporary area, and notify
+everyone that they should test them out ASAP based on the Standard
+Test Plan. </para></listitem>
+
+</itemizedlist>
 </article>
 <!-- Keep this comment at the end of the file
 Local variables: