On Monday 26 April 2004 12:47, Jean-Baptiste CROUIGNEAU wrote:
> I'm not currently a user of Subversion, but I'm searching for a free
> CM, and subversion seems very promising to me.
> However there is some points that seems not addressed by subversion
> (sorry if these points have already been discussed) :
> 1- tasks : I believe subversion can treat groups of files when versioning,
> but it seems there is no task management (ie associate change in any number
> of files/directories to a "task"). Then you would always checkin a task
> instead of a file or group of files, and can reconfigure choosing tasks.
> This could also be linked to a bug tracking tool (as a bug could be link to
> the task(s) that correct it).
You may try trac for this (http://projects.edgewall.com/trac). It is not
_exactly_ what you want, but you can at least create the missing link between
the task (or ticket as it is named in trac) and the commit. And you can also
write some pre-commit hooks which check if there is a ticket number given in
the commit message and fail when no ticket number is given.
> 2- project hierachy : a very usefull feature could be to be able to manage a
project hierarchy, I
> mean link some existing projects (and specific version of each project)
within a global project. I
> think it's mandatory for re-use strategy, especially when your projects are
composed of shared
> modules/toolbox/functions. As Synergy tool (the only one I know well), the
best is to be allowed
> to add any number of projects in any project (ie a true project hierachy,
with as many level as
> needed). Sub-projects can be released or working projects and are treated
almost as directories.
Hmm, this seems like you need some managment frontend for subversion. You
should be able to do all this in subversion, but you have to do it by hand
(which could be much work -- "projects" are just simple directories, which
you can nest the way you like) -- or write some scripts. You should look for
the svn:external property in the documentation.
> 3- others, some less important points : define roles for users/admin,
> (create a new project with a defined directory hierarchy)
Maybe some of this could be done with trac/Apache. For new projects it will be
best if you have some "project-template" directory in your repository.
Everytime you need a new project you simple copy the project-template to your
Sorry, i don't think that an exact solution matching your problem exists. But
maybe you can do many of these things using commit hooks and scripts.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Apr 26 17:38:32 2004