Hi All,
I've used CVS a few years ago and we were managing software artifacts with it
(source files, configs, some docs). I was thinking of setting up Subversion to
manage our software projects, so I figured I'd call repositories based on the
software project names (then trunk, branches ...), but someone here suggested we
could also manage customer projects with Subversion.
I called this post "general artifact management" because I'm not quite sure what
I'm hitting here (SCM/CRM ...). Anyhow, the structure that would be managed
would be of this kind :
- Project#
- SubProject#
- Data (general resources about the SubProject)
- Documentation
- CAD files
- Image files
- XML files ... (any number of directories as a function of file type)
- Customer input
- Deliverables
My fear is that this is not quite the SCM sweet spot Subversion is there for and
I'm not sure Subversion is the best overall tool for that. Or it could be used
to manage the file directories, but maybe some other aplication on top of
Subversion could be used for the rest. The idea is that we would like to be
able to reproduce exactly what was delivered to the customer and potentially
launch deliverable branches. Anyone out there using Subversion that way ?
Any feedback appreciated !
Yves Moisan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 17 17:33:03 2006