Product packaging of the same rule updated by multiple developers in same version for different defects
I have a rule, say PQR, in version 01-02-01 which has been updated by multiple users ( say 5). each of these 5 users are working on different defects and have been asked to package their respective pzinskeys into individual defect zip/jar files ( 5 users -- 5 zips). So, how do I package this rule PQR so that the changes of all 5 users are promoted to the next higher environment?
***Updated by moderator: Lochan to update Categories***
They will be updating one at a time.. How do they know which one is the latest pzinskey.. They will create different zips which will have pzinskeys of the same rule PQR in 5 different zips along with the other rules they modify. They can update PQR randomly and in no sequential order. Challenge is to get all the changes by the 5 different developers on the same same rule in the same version to move to next higher version. How to achieve that?