Handling multi-developer multi-location Jade projects
Posted: Fri Aug 07, 2009 12:03 pm
by Eric Peachey >> Tue, 24 Jul 2001 21:38:22 GMT
Hello,
Currently we have up to 15 developers from up to 5 separate locations working in the same set of schemas in a Jade development environment. Typically there are about 10 concurrent developers building and modying classes and testing the various applications. The development includes a number of background applications as well as one main front end application. Most developer access is via Jade Smart Thin Client unless the LAN is fast enough to support standard client access. The environment is running on Jade 5.1.10.
Given the number of developers and applications it becomes problematic to modify many classes as some process somewhere is likely to be using them. We currently handle this by allowing developers to kill off all running applications so that there is a quiet period when they actually get on and make their changes and do reorgs etc. Generally there will be a 'quiet period' once an hour on the hour so everybody knows that they may be required to stop running the apps around that time. The killing of the applications is handled by notifications. Also certain applications time out if there has been no activity or detect that they are no longer needed (e.g. server execution cache synchronisation process). We also use the Ctrl+Shift+M undocumented feature in the schema browser to broadcast to connected developers to warn of events. This is far easier than trying to ring round and is more immediate than email. The 'Browse classes in use' function is also useful.
How do you handle these and similar issues and maintain an optimal level of productivity in your multi-developer projects?
How many of you out there are working on Jade projects involving over 10 developers in the same environment?
Cheers,
Eric in Dunedin (sunny periods and mild)
Hello,
Currently we have up to 15 developers from up to 5 separate locations working in the same set of schemas in a Jade development environment. Typically there are about 10 concurrent developers building and modying classes and testing the various applications. The development includes a number of background applications as well as one main front end application. Most developer access is via Jade Smart Thin Client unless the LAN is fast enough to support standard client access. The environment is running on Jade 5.1.10.
Given the number of developers and applications it becomes problematic to modify many classes as some process somewhere is likely to be using them. We currently handle this by allowing developers to kill off all running applications so that there is a quiet period when they actually get on and make their changes and do reorgs etc. Generally there will be a 'quiet period' once an hour on the hour so everybody knows that they may be required to stop running the apps around that time. The killing of the applications is handled by notifications. Also certain applications time out if there has been no activity or detect that they are no longer needed (e.g. server execution cache synchronisation process). We also use the Ctrl+Shift+M undocumented feature in the schema browser to broadcast to connected developers to warn of events. This is far easier than trying to ring round and is more immediate than email. The 'Browse classes in use' function is also useful.
How do you handle these and similar issues and maintain an optimal level of productivity in your multi-developer projects?
How many of you out there are working on Jade projects involving over 10 developers in the same environment?
Cheers,
Eric in Dunedin (sunny periods and mild)