Re: Defining branch life-cycles in subversion

Greg Dickie <greg@max-t.com> writes:

> Well it just doesn't make much sense to me I guess. If I want to
> know what state a branch is in for example ( working,
> ready_for_review, rejected,approved ) where would I look for that? I
> guess I could make it work but then I'd be carrying those properties
> over on each subversion of the branch directory....

I can't tell if you really understand how branches work in subversion
or not. If you haven't already, be sure to read the Book's chapter on
branches, or the Design document section on the filesystem. It sounds
like regular versioned properties are exactly what you want.

If you attach a normal versioned property to a branch (which is just
an ordinary directory), then it will automatically persist from
revision to revision. People can come along and change the value of
the property whenever they want. Your workflow system can query the
property to know the 'workflow status' of the branch directory. Seems
pretty simple.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 8 16:47:06 2002