see my responses below... Laurent Michenaud wrote: > > Ok, but i've got a lot of question about the organisation. > Here how i would see the cvs server for our case : > - There would be a cvs server with different branches( stable, > developpement... )
Unless there is a major structural difference between products (like version 4 and version 5 of the same product), we have found it is best to have a single repository for a product. I guess it is a little tough if you have several versions that you are working on currently. Perhaps it is best to start a CVS repository at a major release. At that point you create a branch for bug fixes and retain the main trunk for major upgrade work. The theory is, that as you make changes in the bug fix branch, you merge those fixes into the main trunk. We make interim releases (tags) off our bug fix branches when necessary. > - Each developper would get a version, work it on local and then update > it( i don't have > any ideas about the times per day of update ). CVS is very flexible. You work on your own copy of the main trunk, or branch, and then commit your changes at your leisure (or a policy). If there has been changes to a source file that your are attempting to commit, the system tells you, and you then update source (that you may have changed), and CVS will try and fold your changes into a new version. It will let you know if it finds "Conflicts", it is pretty brilliant about it. I will often run diffs between the repository version and a version that I have modified to see what is different before I do a commit, but it has never been absolutely necessary to do, just a matter of interest. The wincvs client is really very clear about what files have changed, what version (tag or branch) that you are working on, etc, etc. It makes using CVS really simple for programmers that dont' want to get into the details. > - Each developper would have a local tomcat on his machine( not very > good i think ). This is how we work. everyone has their own tomcat. > - Our web server would check the cvs server for the latest stable enough > sources. > The tomcat on the web server would be used only for global testing. > Am i right ? You can certainly set it up this way. I have scripted nightly builds off cvs that use a nominal version. That is, most of our development is being done on the same branch, and that is the version that testers need to see updated daily. > > Do u see others points ? > We have no experience at all about cvs in our enterprise and it's quite > worrying. I had to implement it here after only being a "user" at another organization. I never was aware of a most of the features as a user, and as a CVS administrator have gained a great appreciation for it. > > a+ > > De : Samuel Rochas [mailto:[EMAIL PROTECTED]] > Envoyé : mardi 20 novembre 2001 15:26 > À : Tomcat Users List > Objet : Re: CVS > > Bonjour, > > Laurent Michenaud wrote: > > > > Would be CVS a good thing for our environnment ? > CVS, or any other configuration management tool is a must while having a > team working on a project. You can use some free tools, like the CVS > with clients like WinCVS. You can use some (mostly quite expensive) > commercial tools if you like. > > > Are there any model of organisation that we would use ? > all what you need is a file system and a network connection between the > users. > Take a look at http://www.gnu.org/manual/cvs-1.9/cvs.html and > http://www.cvshome.org/ > > Slts > Samuel Rochas > -- > SWIPe Software Engineering & Project Management GmbH > > Solutions with Individual Profile > > Web: http://www.swipe.de > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> -- Keith Simpson Skillview Technologies [EMAIL PROTECTED] (603)-382-9882 -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
