Defining branch life-cycles in subversion

Hi,

  I'm trying to put a layer on top of subversion in order to enforce a
development process with things like code reviews, automated merging, etc. I
hace done this before with clearcase. I was thinking I could use unversioned
properties on a branch URL to keep things like state information but I guess
I didn't understand how properties were implemented.

Has anybody done something like this yet? I'm thinking I can maintain the data
somewhere outside of subversion but I'd prefer a more elegant solution if
anyone has any ideas.

Thanks,
Greg

-- 
Greg Dickie
just a guy
Maximum Throughput
greg@max-t.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org