Re: Defining branch life-cycles in subversion

Greg Dickie wrote:

>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....
>
>
yes, that lets you keep track of when changes to it's status occured and
things like that... for example:

joe branches to do some development:

$ svn cp http://svn.foo.com/repos/trunk
http://svn.foo.com/repos/branches/joe-wip

he then sets a property on the branch to indicate it's status (my syntax
may be off, i don't have svn in front of me right now)

( in a working copy checked out from joe-wip)

$ svn pset foo:branch-status in-progress .
$ svn commit

later, he has made some changes, so he emails his technical manager, who
reviews the code.

$ svn pset foo:branch-status in-review .
$ svn commit

the manager aproves it, so he notes that and emails joe to tell him to
merge it in.

$ svn pset foo:branch-status approved .
$ svn commit

joe merges the branch and notes that it's been merged.

$ svn pset foo:branch-status merged .
$ svn commit

joe's boss reviews the merge, sees that it has been completed
successfully, and resolves everything in the bug db. joe now deletes
the branch.

$ svn rm http://svn.foo.com/repos/branches/joe-wip

is this something like what you were thinking of?

-garrett

---------------------------------------------------------------------
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:44:34 2002