On Monday 22 January 2007 10:02, Steve Bakke wrote:
> Please at least admit the fact that Subversion tags do not really
> implement the use-case of identifying the ³status² of a set of files.
> You can use Subversion tags for this, but itıs really just an
> approximation. For instance, I would really like subversion to support
> this use-case:
Right, I wouldn't use tags for this use case, I'd use properties.
> * In working on several files at the head of tree, I run through a series
> of quality checks. Upon meeting quality criteria of a given type, I
> apply a status tag to this file.
> * Later, I gather all of the files with a particular status or tag to
> create a release branch or more conventional tag.
This is exactly the kind of thing that properties are for. You can even use
hooks to enforce arbitrary rules on them (e.g. can't have the same status
in two back-to-back versions, or can only be set to a certain status by
members of a certain group, etc)
Granted, it would be handy if the command-line client had build in method
for querying a group of files that have a specific value set as a property,
but this is pretty easy to do with a simple script.
Wesley J. Landaker <firstname.lastname@example.org> <xmpp:email@example.com>
OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2
Received on Mon Jan 22 20:29:52 2007
- application/pgp-signature attachment: stored