Re: Tool support for proposal/approval/commit process?

Schmitt, Michael wrote:
> Hello,
>
> in many open source projects, it is a good tradition to send a patch to
> the developer's mailing list first and wait for approval by a second
> developer, before the patch is actually committted.

I was toying with this idea. I had also considered having a tool accept
a patch, copy the trunk(or the user-designated base) to a new branch and
apply the patch there. Then, anyone wanting to test the patch could
switch a WC to that branch.

The patch could be tweaked (with version control) and once accepted
could be merged back into it's base(trunk). (I can definately see where
native distributed development support could be useful.)

One problem I thought of was that moves/adds/deletes can't be
represented as diffs, so they couldn't be handled in the original bug
opening. I guess one could submit a ticket without any changes, then
commit your moves/adds/changes/patches to your new ticket branch.

Just thinking out loud...

-- 
Andrew Thompson
http://aktzero.com/
Interested in a hosted SVN repository? Email me, let's talk...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org