Re: [Plplot-devel] Subversion-related changes for our next release.

[Hazen B. <hba...@ma...>]

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. Note that the last instruction in  
README.Release_Manager_Cookbook is that the RM should commit the tag.  
As you suggest, the RM could also commit the tag at the start of the  
release process. I imagine generally there will be little difference  
since there typically won't be any changes necessary for a successful  
release. However, if there is, or say the RM would like to play  
around with a tag for the purposes of practicing with svn, debugging  
release scripts, etc., the local tag approach seems to me to be cleaner.

-Hazen