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

re: Workflow orchestration and Subversion

From: Dan Shookowsky <dshookowsky_at_gmail.com>
Date: 2007-10-17 20:30:20 CEST

I'm not actively doing this, but I see moving towards it. The general
process that I envision would be that a developer commits their code as
normal and then branches/tags their code in a given location (e.g.
/branches/Unstable). That would trigger an email to code reviewers,
testers,etc. After evaluating the code the reviewer would tag the folder
with an attribute (confirmed via a hook that the user has authority), that
would trigger promotion to a new environment via svn export or to a new
branch (e.g. branches/Stable).

The hooks would really depend on your needs, but I don't see any reason why
you couldn't handle parallel and serial workflow scenarios given the tools
that are available (on any platform).
Received on Wed Oct 17 20:30:55 2007

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