Thanks for your answers. A few comments;
Ben Collins-Sussman wrote:
> 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.
Hmm, how much of this can be hidden from the user? A lot (umm, most)
of our users aren't savvy enough to understand the in's and out's of
versioning, little less what a branch might be and how to create it. Most of
them will access Subversion through the TortoiseSVH client, and I somehow
need to fiddle with the hooks in trying to make it all seem invisible as
> 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.
Maybe a slight re-write / hack into the Tortoise client could provide
for a way to do this. I guess a specialised version of it in many cases
like mine where the users are ... umm, challenged in the magic ways of
computers, a simplified and controlled client with hooks into a system
that somhow controls commits from certain users?
> ... 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.
How can I use it? Do you mean an application that simply reads the
repository using the API?
> Yes, someday we hope to have a SQL back-end, or even a plain filesystem
Any finger-in-the-air, rough guide to when? :) Our whole shebang is
saturated with Oracle, and some would like to keep it that way.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Feb 13 04:33:06 2004