Developing in Jade 6.1 with multiple developers

[ConvertFromOldNGs]

by cnwam1 >> Mon, 9 Oct 2006 21:02:35 GMT

Does anybody have any recommendations, or would like to share their experience, of developing in Jade 6.1 with multiple developers.
Is it best to have regular re-orgs to update the current schemas to the latest schemas, or should developers do it when they need to?
Are there any other issues to be aware of?
Any feedback would be welcome.

[ConvertFromOldNGs]

by Alan >> Tue, 10 Oct 2006 9:10:34 GMT

We have had a few problems - probably due to lack of knowledge - method of doing things needs to change. Recommend reading white paper, we are also looking at getting consultant in to help with best practice.

In the past we seemed to be able to work on separate areas of the system without impacting one another to much. Now we need to co-ordinate re-orgs/applying versions with each other alot more.

We have had issues with forms being modified while version is created (controls losing parents)

[ConvertFromOldNGs]

by dcooper@jade.co.nz >> Tue, 10 Oct 2006 17:50:50 GMT

The White Paper Alan refers to is here:

http://www.jadeworld.com/jade/whitepape ... aevolution

The whole paper contains lots of useful info, but in particular have a look at these sections: Development Environment, Deployment Scenarios, and Appendix A and B.

Dean.

[ConvertFromOldNGs]

by Torrie >> Tue, 10 Oct 2006 20:06:58 GMT

We've taken the approach that the development environment should not contain any data. This prevents a lot of the reorg issues as most changes do not require reorgs. A separate test environment is used to test the code.

We use the Patch Control Extensions so each developer works in a patch and can extract their changes into the test environment. For larger system wide changes, we will turn off the patch control extensions and all work in the same patch. It is possible to automate the extractions and loads using JadLoadb (we run this as a fat client from a Jade script within the development environment.) You do need to be aware that Jade allows patches to overlap without any warnings etc unless you implement the security hooks to check for this.

Torrie