[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Commit - Approve cycle ?

From: ²Z <my_at_esast.com>
Date: 2005-08-23 03:11:59 CEST

Hi Karl:
>>but I think the larger challenge here is designing the interface and
I suggest maybe workflow could be reserved implementing in Hook script and
it is flexible for integrating with third party workflow software , but SVN
need an interface in Hook script for enable commit as dangling or let the
tranaction pending, and third party workflow software could call SVN api to
continue or reject pending tranaction to do final commit

-----Original Message-----
From: kfogel@newton.ch.collab.net [mailto:kfogel@newton.ch.collab.net] On
Behalf Of kfogel@collab.net
Sent: Tuesday, August 23, 2005 4:42 AM
To: my@esast.com; Chia-liang Kao
Cc: dev@subversion.tigris.org
Subject: Re: Commit - Approve cycle ?

Chia-liang Kao <clkao@clkao.org> writes:
> Max Bowsher <maxb <at> ukf.net> writes:
>>> Ben mention it could be implement by committing changes to a transaction

>>> but
>>> then just leave the transaction alive rather than committing it
>>> But how to
>>> achieve this feature ? Did it need to modify SVN source code or just
>>> implement it in Hook script? And How to let the pending transaction
>>> commit to repository? Any comment will be appreciated
>> It would require lots of new code.
>> What exists so far is just the capability of the repository to store an
>> uncommitted change. Very little of the logic to make use of that
>> capability exists. In practice, just have developers commit to
>> personal branches, and have the manager merge to trunk.
> Also you will have to update the uncommitted transaction with textual

I actually disagree that this would require lots of new code. Also,
it does not require updating the uncommitted txn with merges -- that's
a further enhancement, not a necessity for the basic feature.

What Subversion needs is a small change, a way to commit such that the
txn is left dangling. Then the bindings offer the rest of what's
needed. Of course, new code would need to be written around
Subversion, but I think the larger challenge here is designing the
interface and workflow. The actual coding task is not so large.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 23 03:12:56 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.