Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Multiple Developers...
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire de projet
Divers
Thread ID:
00507340
Message ID:
00507389
Vues:
19
>>to all
>>we have multiple developers working on the same project. in order for this to work efffectively we have to copy the project to our local hard drives and then copy our changes to the master copy on the server. is there a way to have multiple developers work on the same project at the same time without having to copy it locally.
>>tyi
>>fc
>
>We dont use Visual Source safe here. I guess it never really worked all that well in all situations for us. So here is what we do.
>
>Master files reside on the server. These are all the files needed to provide a build of our application. We have one person in charge of builds and of our library. To ensure that nothing gets added or removed without approval first.
>
>Then all the developers have their own directory on the server where they use copies of the master libraries and their own data. When they make changes or updates then they have the environment to test it out fully. Once they are happy, then they inform the master librarian that they wish to update their portion of the Master application. The librarian does so and then produces an interim build for the developer to test. Once it is tested then the changes will be included in the next build.
>
>All our developers work on their own portion of the master application. We dont overlap (I work on Configuartion Management, another on Drawings, etc..) so we are not clobbering each other. But we all do work with the same master libraries and controls for our forms and all. So if I see something that needs changing in the master libraries (application object, classes, etc) then I work through the master librarian to do it (since we put in many hours developing and application object, changes are rare now). Thus it is the librarians job to ensure my suggested changes dont kill someone else. The librarian is just another developer so they should know the whole picture.

Hi Bret,

We use the same approach here and I'm not happy about it. First of all, since I'm not the person, who is responsible for our classes update, each change, which I think is necessary, I need to explain in lots of e-mails to finally have a rejected message or implemented it not the way I wanted.

Another problem:

We have a Developer server, a Live server + each developer has his/her own local copy of everything. The task of maintaining all these systems in sync seems too complicated. I finally mostly work on the Developer server itself, not on my local drive, since it has outdated applications anyway... Sometimes I forgot to make a backups, so it may lead to some serious problems. Fortunately enough, I always know, that I'm doing...
If it's not broken, fix it until it is.


My Blog
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform