[Sandev-cvs] sand/platform/docs ReleaseProcess.html,1.3,1.4

[Eric P. <th...@us...>]

Update of /cvsroot/sandev/sand/platform/docs
In directory sfp-cvsdas-3.v30.ch3.sourceforge.com:/tmp/cvs-serv21001

Modified Files:
	ReleaseProcess.html 
Log Message:
Minor verbiage improvements and adjustments.


Index: ReleaseProcess.html
===================================================================
RCS file: /cvsroot/sandev/sand/platform/docs/ReleaseProcess.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** ReleaseProcess.html	19 Aug 2006 20:58:30 -0000	1.3
--- ReleaseProcess.html	14 Aug 2010 17:39:20 -0000	1.4
***************
*** 8,12 ****
  <p><center><h1>sandev release process</H1></center></p>
  
! <p>Here's what we currently do when creating a release: <ol>
  <li>Verify all work for the release is complete and tested.
  <li>Verify we are using recent Ant and container releases.
--- 8,18 ----
  <p><center><h1>sandev release process</H1></center></p>
  
! <p>Here's the complete process for creating a release.  The steps here
! are all from things that have bitten us at one point or another.  If
! you do all the steps, then the chance of a fully functional release
! that can be installed and used by other people is pretty good.  If you
! skip some of the steps then you run the risk of potential problems. </p>
! 
! <ol>
  <li>Verify all work for the release is complete and tested.
  <li>Verify we are using recent Ant and container releases.
***************
*** 36,41 ****
      a clean box.  Build and run to make sure nothing was lost in transit
      except the CVS directories.
! <li>Update <CODE>mainbuild.xml</CODE> with the next release number, and
!     reset release.txt for the next release.
  </ol></p>
  
--- 42,48 ----
      a clean box.  Build and run to make sure nothing was lost in transit
      except the CVS directories.
! <li>Update the <code>publish.releasename</code> property in 
!     <CODE>mainbuild.xml</CODE> with the next release number, then clear
!     out <CODE>release.txt</CODE> to ready for the next release.
  </ol></p>