On May 20, 2007, at 7:48 PM, Alan W. Irwin wrote: > [..] > > Of course, once you have found a set of svn commands that work for > making a > tags subdirectory corresponding to the release, then you will want to > document those commands in README.Release_Manager_Cookbook.
I've made a first pass at this. It'll only really been finalized once we've been through it once. > When the time comes, let me know if there is any way I can help you > further > (especially with any of the shell scripts that need modification) > with the > changes imposed on the release process by svn. Ok. Could you make the following changes to scripts/make_tarball.sh? 1) Remove the archive tagging stuff. 2) Uses svn export on a local directory to create the build directory. Example: debian ~/temp/plplot-test : svn export ~/OpenSource/plplot/tags/v5_7_4 Where ~/temp/plplot-test would be the release build directory (/tmp/ plplot-dist-prep?) and ~/OpenSource/plplot/tags/v5_7_4 would be the directory that the script was originally executed in. As outlined in README.Release_Manager_Cookbook, the new approach is going to be create a branch in the tags directory for the release. 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. thanks, -Hazen ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
