subversion transactions

[Bosnjak Zoran ITWEP <Bo...@iskratel.si>]

Hello all,
I refer to old mail (Ben Sussman) from the subversion mailing list (see below).
Can someone please explain how can one generate and examine the transaction.

My idea of the workflow is following:
1. person A does a checkout of the main trunk
2. A makes modiffications
3. When A is about to commit, he generates a 'transaction' and sends it to B for review
4. B uses this transaction to make his working copy the same as A's and starts examine
5. B put his comments into each file property (for example), B can also correct some files itself
6. B makes a new 'transaction' out of his working copy and send it back to A
7. A updates his working copy with transaction from B
8. A makes some more corrections (comments from B)
9. Finally A makes commit to the main trunk.

Please confirm if this scenario is possible (with some extra scripting around svn). How to generate a transaction from working copy and how to apply it on someone-elses working copy (without doing actual commit to some temporary branch)?
Do you have any other idea to do formal code review before commit.

Thanks for your answer.

regards,
Zoran Bosnjak

------
Subversion certainly has the foundation laid out for you... in theory, a
commit transaction can live indefinitely, and a reviewer can examine it
before committing it.  A simpler solution is to have people commit every
change to a real branch directory, and then have an "integrator" merge
each branch to the trunk, and then delete the branch.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: subversion transactions

[Ben Collins-Sussman <su...@collab.net>]

On Jun 23, 2005, at 8:32 AM, Bosnjak Zoran ITWEP wrote:
>
> Please confirm if this scenario is possible

No, it's not possible using existing svn binaries and tools, nor will  
scripting help.  When I said that the "foundation is laid", I merely  
meant that the *APIs* already exist which could allow the things you  
describe to happen.  But you'd have to write your own custom clients  
and tools to make use of such APIs.

That said, there's no need to undertake such a huge project.  You can  
accomplish the same effect just using branches.  Have each user  
commit changes to a private branch, and then have others review and  
comment on it in the branch.  (Anybody can 'svn switch' their working  
copy to any branch, back and forth.) When everything is all approved,  
then merge the branch to /trunk.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org