From: Cameron S. <ca...@sh...> - 2003-09-15 08:27:46
|
On Sunday 14 Sep 2003 8:10 pm, Sean Wheller wrote: > The permeations of this theory can spin our heads for > a year. So I ask the > question. Is CVS the tool for the job? Perhaps we need > CVS and an XML > Database, maybe just the database with an application > layer above it. CMS > and KMS? What tools do we recommended and what tools > do we use. CVS is the de-facto standard of open source projects. It is likely to be replace by subversion in a year or 2, however subversion is just a rewrite of CVS and will have CVS imports. Hence it would take a lot to convince me that we should not use CVS. With regards to releases and whether we access sections on a per file basis or per release basis: Ie, should we reference: /project/<release>/file.xml or /project/file_<version>.xml Again, I refer to convensions in releasing standards and software libraries. In both cases, projects convensionally provide releases. It is possible for the version of a file in one release to be the same in the next release. While I acknowledge that documentation could logically be released on a per file basis, it would make referencing the documentation more complicated. In this case, I think we should sacrifice flexibility in order to Keep It Simple. -- Cameron Shorter http://cameron.shorter.net Open Source Developer http://generguide.sourceforge.net http://mapbuilder.sourceforge.net http://geotools.org Senior Software Engineer http://www.adi-limited.com |