Re: A few questions

Alexander Johannesen wrote:

> How do you best handle a workflow situation where committers
> committ to the system, but administrators must approve their
> changes before allowed further?

Have every committer commit their change (feature, bugfix, whatever) to
a private branch. Use an external communication system for notifying
managers that branches are "done" and ready for review. If the manager
approves of the change, then somebody (either manager or coder) merges
the branch to the main trunk, and then deletes the branch.

Subversion has no built-in workflow system. At best, you can use
Subversion's metadata properties to help. A programmer can set a
property on his branch that indicates that it's ready for review, and a
manager can change the property to indicate that the branch is ready to
be merged into the trunk. You need to invent a system that works best
for you.

> If we store things in the metadata repository, does it exsist
> hooks to link these to other systems?

I'm sure external workflow systems can be taught to store their own
metadata in Subversion, or, conversely, to read metadata from
Subversion. But that's an integration problem you need to solve
yourself. Subversion provides very general versioned metadata; you
need to figure out how you want to use it.

> Some have stated some unstability with BerkleyDB. Any plans on a
> replacement, ever?

Yes, someday we hope to have a SQL back-end, or even a plain filesystem
back-end.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 13 03:26:20 2004