On 2007-05-20 16:34-0400 Hazen Babcock wrote: > > On Mar 31, 2007, at 2:52 PM, Alan W. Irwin wrote: > >> Note, during the release process we use throwaway tags which are created >> by >> make_tarball.sh and then thrown away again by rm-cvs-tarball-tags.pl once >> everything is working properly. From my reading, I believe you create tags >> by "svn copy" of the top-level trunk directory to a specifically named >> subdirectory of the tags directory at the top of the repository, and you >> remove those tags by "svn remove" on the directory you created. The svn >> book >> does say this process is cheap (everything done with the equivalent of >> symlinks) under svn so I think we should just go ahead and continue to use >> throwaway tags with the appropriate changes from cvs to svn syntax. I >> would >> appreciate you having a look at the tags section of the svn book, and >> letting me know what you think. > > I've just finished reading the svn book (through chapter 4 anyway). Based on > this I'd suggest the following for the release flow: > > 1) Create (using copy) a new (local) sub-directory in the tags directory that > is a snapshot of PLplot for the release. > 2) Run make_tarball.sh in this directory, where make_tarball.sh is suitably > modified so that it just makes the tarball from the local repository. > 3) Assuming that the tarball checks out ok, the RM commits the local > tags/new_release directory to the Sourceforge repository & uploads the > tarball, etc. as before. > 4) If the tarball doesn't work out for some reason, the RM merges in the > necessary changes from trunk to get it to work.
I don't see anything wrong with your suggested approach. My understanding is that svn tags are really just an svn convention for stuff stored under the tags subdirectory. They are not in any way identical to CVS tags which are absolutely frozen at one snapshot. For example, as you have noted above, you can change an svn tags subdirectory after it is first created. Furthermore, it sounds like you know a way using "svn merge" (I am not familiar with that svn subcommand, yet) to update a specific tags subdirectory so that it reflects a particular revision (probably the latest) of the trunk that you want to use for the release. 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. 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. 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
