...

When we complete that, we also need to prepare for the Clone. We prepare for the Clone by making sure nothing is left in-flight. Meaning, nothing 'In progress'. Everything must either be Ignore or Complete, including the work from Fruition for remediation.

At that point, make next revision 5 of the spreadsheet, that contains the last things that were still 'In Progress'. Either they'll be getting ignored, or they'll be getting set to Complete. We need to have Fruition stop building Health Check Remediation things in DEV, if they have not stopped already.

...

• Pick each one individually
• Make an export, save with a descriptive name. The default name is ridiculous. Must manually rename.
• repeat until completed
• That will probably take a few hours; want to be methodical and thorough.
• Then double-check through the files, and make sure we have everything.
  

The script for dumping XML update set exports

Dan Franko has an Aptara script that can dump out the contents of the update sets. He's fixing a minor bug and giving it a try.

How to re-apply in the future

...

• System Update Sets -> Retrieved Update Sets. Scroll to very bottom of the page, and select Import XML.
• Provide the file. 
• Once an update set is imported into DEV, it will just be a local copy until the update set is applied. 
• Admin will need to Preview, resolve issues with Preview, then Commit.
• Commit order will need to follow the order specified in the documentation relevant to the Requirement being restored. See spreadsheet and supporting documentation about the order the update sets were applied to TEST when they were under development.
• The folder structure is confusing, and is based on the spreadsheet. If you have trouble finding an update set, just use the find command on unix or similar trick to navigate the tree while searching for the file pattern.
• Backeberg had proposed merging the update sets before export, but it was decided not to do that. Merging would have dramatically shrunk the collection of update sets to retain and reapply in the future.

Auditing the update sets

Backeberg walked through the collection of update sets, and cross-referenced those with the zip file from the box share. He found a full collection of update sets, and set the clone over DEV for Aug. 1, 2014.