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

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

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

Modified Files:
	ReleaseProcess.html 
Log Message:
Updated the release steps a bit to reflect changes to sourceforge and how
we work.


Index: ReleaseProcess.html
===================================================================
RCS file: /cvsroot/sandev/sand/platform/docs/ReleaseProcess.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** ReleaseProcess.html	14 Aug 2010 17:39:20 -0000	1.4
--- ReleaseProcess.html	19 Aug 2010 23:39:42 -0000	1.5
***************
*** 30,48 ****
      <li>Make sure the TaskHeapDemo UI comes up
      </ul>
! <li>Tag the tree in CVS as sandev_x_y (select sand, 
!     Modify|Create a tag on selection)
  <li><code>ant publish.docs</code> (publishes the release documentation)
! <li><code>ant publish.release</code> (srubs and creates the release file)
! <li>Log on to sourceforge and create the release.  Post the 
!     <a href="release.txt">release text</a> into the release notes and
!     a corresponding news item.  Preserve the preformatted text so the 
!     line breaks come through.
! <li>After the files all post (it can take a few minutes for them to show
!     up), verify the news is readable and download the release file onto
!     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>
  
--- 30,58 ----
      <li>Make sure the TaskHeapDemo UI comes up
      </ul>
! <li>Tag the tree in CVS as sandev_x_y
! <!-- Used to publish docs to sandev.org but nobody reads it so it is not
!      worth doing anymore
  <li><code>ant publish.docs</code> (publishes the release documentation)
! -->
! <li><code>ant publish.release</code> (scrubs and then creates the 
!     release file leaving it above the top level sand directory).
!     Upload the release file to sourceforge using their admin interface.
! 
! <!-- It doesn't seem like this is part of the sourceforge interface 
!      anymore, or at least it wasn't easily accessible and the download
!      link was created automatically.  If this gets to be part of their
!      process again then uncomment this step.
! <li>Create the release, pasting the <a href="release.txt">release text</a> 
!     into the release notes and a corresponding news item.  Preserve the 
!     preformatted text so the line breaks come through.
! -->
! 
! <li>Download and verify the release file contents.  Should have everything
!     required to build without any 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>