On Wed, 27 Oct 2004 09:20:53 -0400, Mark Phippard
<MarkP@softlanding.com> wrote :
> I think what you would
>want to do is the pretty much the same thing, except do it on the client.
>Create a "svn-commit" script that your users use instead of svn ci. The
>script would do something to update a file, or a property on that file and
>then run svn ci. That would cause that file to be included in the commit,
>and would allow you to then use the LastChangedRevision keyword in that
>file.
Okay, this sounds like a possibility. I think everyone with commit
privileges is running a system that could run such a script.
>The one thing I have not seen, is why it is so necessary to have this
>information in a file to begin with? Why can't you just use a more normal
>release process and use Tags for your releases?
We do that for normal releases; this is for daily snapshots. Those
are produced by a number of different people, operating on different
schedules. For example, I produce binary builds of the Windows
versions of the trunk and patch releases several times per week.
There are also daily tarballs of the source produced for people doing
their own builds, and there may be binary builds for other platforms
too, I'm not sure. Each of these is produced at a different time.
We could standardize on a daily tag, and always build the snapshots
from the last of those: but that would slow the release of bug fixes
by a few hours, it would load up our log file with all those entries
where the tag was created, and it would be inconvenient: now I do
svn update
hack, build, test
svn commit
upload
and if we followed this scheme, it would be
svn update
hack, build, test
svn commit
svn switch <tag>
build, test
upload
If I fix a bug and commit it, I'd like to do a build from my
up-to-date source, rather than switching to a tag release and
rebuilding from that.
Duncan Murdoch
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 27 15:52:10 2004