> * The ReleaseHelper script cuts the release directly from the CVS
> repository -- but first, the repository is now SVN, and second,
> the SVN version has version tags in the Properties and html files
> instead of the actual version which must be first replaced by the
> actual version with "setversion.py" before making the tarball.
Just had another look at it and I think I understand: You make a tag,
replace the version tags, check this in under the tag and then cut the
release directly from the tag. The trunk keeps the version tags. Right?
I was a bit confused because usually, tags are not changed after they
have been copied. I will document this in the ReleaseProcedures.
Still, is there a newer version of ReleaseHelper that uses SVN instead
of CVS and that handles the ReleaseNotes-X.Y files properly? For the
tag, they should be *moved* to ReleaseNotes-0.9, and in the tag if it is
a final release, they should be *copied* to ReleaseNotes-0.9, and
ReleaseNotes-X.Y should be emptied (prepared for the next release).