I've been developing for more than 4 years, and almost every clone event causes some degree of negative consequences on my works in progress. For my most recent trauma, I had been developing a novel approach to a multi-form view application that spanned over 5 or 6 releases, so while I had been updating our TEST instance, the majority of work was still in DEV, and very few of my update sets had been migrated to PROD. After the clone over DEV and TEST, I began the recovery by retrieving update sets, getting out of sequence and causing major damage to a fragile collection of complex form views along with a series of refinements to some important client scripts. It took a week to recover.
Can anyone offer a link to a checklist or simple knowledge article to help me understand how good developers get it right? I think my most recent mistake was not pushing the updates in the releases; if I had taken an aggressive approach to publishing a "less-than-mvp" product for the sake of maintaining order in sequences, my pain may have been more tolerable. But right now I am stinging, and embarrassed.
I can find plenty of "how to clone" articles written for admins, but there is no guidance for developers for pre-clone and post-clone recovery best practices; I welcome article suggestions.
Thank you all in advance,
woody
