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

Re: About general artifact management

From: Yves Moisan <ymoisan_at_groupesm.com>
Date: 2006-05-19 16:42:32 CEST

Andy Levy <andy.levy <at> gmail.com> writes:

> It's not a common scenario, but people do use SCM systems as document
> repositories without any code in them at all. You just don't hear
> about it often.

Hi Andy,

Indeed that's exactly what my email to the list wanted to trigger : reactions
from folks using SVN to manage not only code (because we will have some code to
manage within customer projects) but deliverables and other artifacts as well.
In fact, I know SVN is used to manage code artifacts mainly so I wanted to know
in what kind of an ecosystem people use SVN to have an overall project artifact
management environment.

Indeed it may be that Trac can be used to manage some aspects of it but what we
are basically looking for is a way to tag a project, which could include code
tags (e.g. r345 of SVN project X was sent as part of deliverable X) and
potentially other artifacts like reports.

Thanx for your input !


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 19 16:46:33 2006

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

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