Driving towards Bugzilla 3

[Gregary Hendricks]

>>I think what we've more or less decided at this point is that our CVS
>>repository is very poorly laid out at the moment, and needs to be
>>reorganized (as well as the installation location of files so the
stuff
>>that the webserver isn't supposed to see doesn't have to be under the
>>docroot of the webserver).  When this reorganization happens, it's
more
>>than likely it will break people being able to upgrade a live
production
>>installation via CVS in place (it would have to be moved out of the
>>docroot then upgraded, then reinstalled back to the docroot).  That in
>>itself seems like a very good reason to bump the version number, since
>>people expect major installation process changes when a major version
>>number changes.

>That's fine, but why not switch to svn at the same time.  The fact that
>you can't move files without breaking people following along in cvs is
bad
>bad bad and svn fixes this problem which makes it good good good.  :) 
 
I will add my vote to switching to subversion. We have been using svn
for our bugzilla development and are very pleased with the
functionality. 
It also makes merging branches a breeze. That is how we were able to get
the rc3 code merged into our rc2 customizations. 
Besides, svn supports directory changes. Need I say more :) 
 
--
Greg Hendricks 
 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20041210/a478fd8c/attachment.html>