How to know the correct sequence of update set committed date.

[VIKAS MISHRA]

I have 13 update set those are completed and moved to QA and commited in QA

due to upgrade i have took backup of all the update set frrom dev instance not from QA and in DEV ther was no commited date so i took sequence on the bases of created date. 

colnning of dev and qa has done from prod. upgrade is also done. 

Now when i moved all the update set in DEV and QA back and commited found so many issues becuase the sequence of update set should be from committed date not from create on date. 

Please suggest how can i get the correct committed date sequence when now no old update set is there in QA to show me the sequence.

[Uncle Rob]

Yikes.  I don't know how you're going to do that now that your source for the commit times is blown away.
This is why I always sequence my update sets in the title if they're related to each other.

Far as I can see you have a couple strategies.

1)  Look at the actual update xmls and not the update sets.
Get one list of all those updates across all the update sets and see if their created date gives any kind of obvious ordering to the update sets.  Weakness here is that it assumes the update sets were meant to be deployed roughly in the chronological build order.

2)  Get all the people involved
Find everyone who helped build those update sets and have a big long meeting about it.  Each dev is likely to know the order of their own update sets + what other update sets they depend on.