Update sets with multiple developers

[koliva]

I have been the only developer at my organization until recently.   I have been in my role only a year and have experienced many issues with moving update set from dev to live (I only have the 2 instances).

I have been told that I should open and complete an update set before opening a new update set; this is what I have been doing.   If something urgent comes up that I need to fix something, I complete the current update set and load/commit into live so I can then open a new update set in dev to look into the urgent matter.

Now that there are two of us, how can we both work on the same development instance either working on the same project or two different projects?   How can we both have 2 update sets open at the same time??

[AdityaTW]

You can have multiple update sets open at a time - when you are ready to move the final updates to the next environment, you just merge them into one update set.

For workflow - our practice is to have developers work on the same update set to maintain the historical information of that workflow (checkout, publish).

There also needs some form of communication between developers to ensure they don't step on each other's toe. Typically the lead developer reviews the update set before it is moved to the next environment to see any glaring issues.

In Eureka (or maybe Dublin) there is Team Development - you may want to review that in WIKI if you run Eureka.

[antonymirza]

It doesn't matter how many open update sets you have. Important is yo be sure which one is marked as current...

Plus be aware that not many people are working on same script etc. which I believe is easy in ur case considering the team size....