Our opinion:
- A team can't be to small to use version management.
(I wouldn't even work with out vm if I where alone)
- CVS does a good job in version management
- CVS has some drawbacks, due to its history
(no transactional check in, handling of directories
awkward, it's sometimes hard to write own scripts
to extend CVS because the outout of several commands
is not formatted in a way that is easy to process)
- Use CVS in way where the checkout are read only
and the users user cvs edit to edit the files
- Setup one repository for all projects
- Give it a structure like:
cvsrep
- common
- projects
- project 1
- project 2
- Use CVS for all files, not only java and jsp.
- Write Scripts (Make/Ant/Shell) that create a website
from the repository
- Let your developers checkin often
(ideally several time a day. The checkin should a least
be syntactically correct, better functional correct)
Benfits:
- Roll back to a previous version
- Who changed what
- What changed since last online version
- Merge of changes by two developers
- Create bugfixes for previous releases
without the need to update
> -----Urspr�ngliche Nachricht-----
> Von: Laurent Michenaud [mailto:[EMAIL PROTECTED]]
> Gesendet: Dienstag, 20. November 2001 15:04
> An: [EMAIL PROTECTED]
> Betreff: CVS
>
>
> Hi,
>
> I work in a web agency and we are studying the use of CVS.
> We are 3-4 developpers per project.
> We have a linux web server with tomcat/apache.
> For the moment, we are working on shared sources via samba.
>
> Would be CVS a good thing for our environnment ?
> Are there any model of organisation that we would use ?
>
> Please tell me about your organisation if u use cvs, what benefits....
>
> Thanks
>
> Michenaud Laurent
> - Adeuza -
> [ D�veloppeur Web - Administrateur R�seau ]
>
>
> --
> 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]>
