We're trying to do something a little more file-centric than Subversion
likes and I'm looking for thoughts on our problem.
We have a need to identify particular revisions of particular files as
'baselined' (e.g., completed peer review, etc.). We need to be able to
identify all files that have been baselined (and ideally, all files
which have not been). A file may be re-baselined if changed. We've
thought through a few different strategies and haven't found one that
works well.
- Adding baseline information to the commit message won't work because
the file has to be committed to perform the peer review prior to
labeling it baselined.
- Revision properties are a possibility, but we'd want to associate the
property to a specific file. Conversely, file properties don't allow us
to also associate the property to the file at a specific revision.
Further, we run into the same problem as above, with doing a recommit of
the file in order to add the property.
- The Subversion tagging mechanism has limitations for dealing with
files. If we tag a file into tags/baselined, we then have to browse the
tags directory to learn which files have been baselined rather than
being able to keep that information with the file in the trunk. Also, we
won't be able to re-baseline a file without deleting it and recopying it
or else maintaining a large directory tree to accommodate multiple
baseline revisions. The former method means that we can't do a log on a
single file to see baseline history and the latter method would just be
a mess.
Any advice you can offer would be appreciated.
Erik Granse
Software Engineer
Tel 651.581.3597
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 19 18:59:14 2005