RE: Commi with Approve Cycle

You can easily deal with this scenario - use branches. If all development changes occur on a branch, then your QA team becomes responsible for merging the branches back to the mainline trunk. (or not, if they think the changes are poor)

I doubt it ever will have an explicit workflow engine adding, SVN is there to store the changes permanently (even if they're not approved by your QA team, you don’t want changes to be held temporarily until QA gets round to viewing them).

You could also use an external tool such as ReviewBoard to assist with your workflow.

> -----Original Message-----
> From: Puig, Juan [mailto:JPuig_at_adium.com.uy]
> Sent: Tuesday, May 12, 2009 8:11 PM
> To: users_at_subversion.tigris.org
> Subject: Commi with Approve Cycle
>
> Hi Everybody,
>
> I would like to know if the current version of subversion still doesn't
> have any functionality to make commits with some kind of approve cycle
> for example a QA person that needs to check every code modified before
> commiting it to the main repository.
>
> As describe in this post:
> http://subversion.tigris.org/servlets/CTSearch?searchText=approving+com
> mits&defaultField=title&Search=Search&pluginName=messages&dsForumId=106
> 5&dsNav=APz
>
>
> Thanks,
>
> Saluda Atte.
>
> Juan Puig
> IT - Aplicaciones Corporativas
> Amedrugs Corp.
> Tel. (+598-2) 518.25.30 Int. 192

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2230573

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-13 08:59:15 CEST