On 2007-05-22 23:11-0400 Hazen Babcock wrote: > > On May 22, 2007, at 2:25 AM, Alan W. Irwin wrote: > >>> The rest of the release build process will then be done working off the >>> contents of this directory. When the release checks out the RM will >>> commit this directory to Sourceforge. >> >> I assume you should commit it when you first create it with the svn copy >> command and after updates which should be rarely necessary since you are >> working with a copy of trunk that presumably has been thorougly tested by >> our core developers. The only exception to this "no updates for tags >> rule" >> I can think of is if you forget some part of the release process (e.g., >> updating a release file) that you catch before you release the tarball at >> SourceForge. In that special case the additional commit required before >> running the make_tarball.sh script would be quite fast since typically >> only >> one file will be changed. >> >> By the way, I think you forgot to comment about the tag commit step in >> your >> README.Release_Manager_Cookbook changes. > > My approach was to keep the tag local until the release was actually released > on Sourceforge.
The previous revision of make_tarball.sh cvs exported from the remote repository (not a local filesystem) with no problems at all so that is the approach I am starting with for svn. (I am being conservative here because we are all pretty much svn newbies.) Later, if your "svn export" experiments show there is a better way to do everything locally until the last moment before release, then bash scripting is so easy you will probably find it straightforward to make the script changes you want, and I certainly encourage you to do that independently. (Our scripts belong to all of us so anyone and especially the release manager should feel free to change them.) However, I would be glad to have a look at your script changes and help you debug them if you feel you need that moral/practical support. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel